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 declare destructiveHint=true and readOnlyHint=false, so the tool's mutating nature is known. The description adds useful context ('previously stored memory', 'clear sensitive data') but does not disclose additional behavioral details such as irreversibility, permissions, or error behavior beyond what annotations imply.
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, front-loaded with the primary action, and every sentence adds meaningful guidance. It has no fluff or redundancy.
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 one-parameter tool with complete annotations and full schema coverage, the description covers all essential aspects: what it deletes, when to use it, and how it relates to sibling tools. No additional details are necessary.
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 only parameter 'key' is described in the schema as 'Memory key to delete'. The description's phrase 'by key' aligns with the schema but adds no extra semantic value beyond what the schema already provides.
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 identifies the resource ('a previously stored memory by key'), clearly distinguishing it from sibling tools like remember and recall. It unambiguously states the action and object.
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 clear usage context: 'when context is stale, the task is done, or you want to clear sensitive data.' It also references related tools by saying 'Pair with remember and recall,' but it does not explicitly state when-not-to-use the tool or enumerate exclusions.
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.
Several tools have overlapping purposes: the four ask_pipeworx variants all route to the same 5,581 tools (ask_pipeworx_beta is currently identical to stable), and the six polymarket_* tools have subtle boundaries between research, edges, and arbitrage that could cause misselection. That said, the descriptions are unusually detailed, and non-overlapping clusters (CSO table tools, memory tools, subscription tools) are clearly distinct.
All names are snake_case and mostly verb-first (get_dataset, resolve_entity, validate_claim), but conventions are inconsistent: polymarket_* and pipeworx_* are brand/noun-first while bet_research and ask_pipeworx put the verb first for the same domains, and some tools are pure nouns (entity_profile, recent_alerts). The pattern is readable but far from predictable.
At 35 tools the server is well past the 25+ 'too many' threshold for a single MCP. Several tools don't earn their place: ask_pipeworx_beta is functionally identical to ask_pipeworx right now, and the six polymarket tools plus four ask_pipeworx variants represent heavy redundancy for what are essentially two sub-domains.
The data-access core is covered end to end: discovery (discover_tools, list_datasets, suggest_questions), structured reads (ask_pipeworx, get_dataset, query_dataset), grounded verification (validate_claim, ask_pipeworx_grounded), comparison (compare_entities), change tracking (recent_changes), plus memory and subscription CRUD. Minor gaps: subscriptions can't be edited (only recreated) and unrelated utilities (generate_llms_txt, scan_dependency) dilute the focus rather than fill a real gap.