forgetDelete a previously stored memory by key. Use when context is stale, the task is done, or you want to clear sensitive data the agent saved earlier. Pair with remember and recall.
| Name | Required | Description | Default |
|---|---|---|---|
| key | Yes | Memory key to delete |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide destructiveHint=true and idempotentHint=true. The description adds usage context but does not disclose additional behavioral traits beyond what annotations convey (e.g., whether deleting a nonexistent key fails silently or errors). With good annotation coverage, the description adds moderate value.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences: the first clearly states the action, the second provides usage guidance. No extraneous words, efficiently front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple 1-parameter destructive tool with no output schema, the description covers the action, when to use, and sibling tools. It lacks details on failure behavior (e.g., missing key), but this is a minor gap given the tool's simplicity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, and the schema already describes the 'key' parameter as 'Memory key to delete'. The description does not add further semantic detail, so it meets the baseline of 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Delete') and resource ('memory by key'), clearly stating the action. It also distinguishes itself from siblings 'remember' and 'recall' by mentioning pairing, making the purpose unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides explicit use cases: 'when context is stale, the task is done, or you want to clear sensitive data.' It also suggests pairing with 'remember' and 'recall', offering context on when to use this tool. However, it does not explicitly exclude alternatives or provide strict when-not-to-use guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have clearly distinct purposes, with a few overlapping pairs (e.g., ask_pipeworx vs ask_pipeworx_grounded, multiple polymarket tools) that could cause mild confusion, but descriptions adequately differentiate them.
Tool names consistently use snake_case, but the verb_noun pattern is not consistently applied; some names are noun_noun (dallas_datasets, bet_research) or adjective_noun (ai_visibility_check), creating a mixed nomenclature.
With 33 tools, the server exceeds the typical well-scoped range. While the broad data domain justifies many tools, the count feels heavy and would benefit from consolidation of related functions.
The tool set covers a wide array of domains (company data, drugs, economics, prediction markets, memory, subscriptions) with only minor gaps (e.g., no direct web search tool, as ask_pipeworx mostly covers it). Overall, it is comprehensive for its purpose.