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 indicate destructiveHint=true, and the description adds 'delete' and 'clear sensitive data', which aligns. The description does not contradict annotations and provides sufficient behavioral context for a simple destructive operation.
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 concise at two sentences, with no wasted words. The purpose is front-loaded, and the usage guidance follows efficiently.
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 tool with one parameter, no output schema, and clear annotations, the description is complete. It explains the purpose, appropriate usage, and relation to sibling tools.
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?
The input schema has full coverage (100%) with a clear description for the only parameter 'key': 'Memory key to delete'. The tool description adds no additional parameter information beyond what the schema provides, so baseline 3 is appropriate.
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 states 'Delete a previously stored memory by key', clearly indicating the verb (delete) and resource (memory by key). It distinguishes itself from siblings 'remember' and 'recall', which store and retrieve respectively.
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 specific use cases: 'when context is stale, the task is done, or you want to clear sensitive data'. It also pairs with 'remember' and 'recall', offering context for its usage. However, it does not explicitly state when not to use it.
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 cluster around similar purposes—the three ask_pipeworx variants, the five polymarket_* analysis tools, and the meta/discovery tools (discover_tools, suggest_questions, pipeworx_trending)—so an agent could plausibly call the wrong one. However, the descriptions are exceptionally detailed with explicit 'use this when' guidance, which mitigates most confusion.
Names are almost all snake_case, but there is no consistent verb_noun or resource_action pattern: ask_pipeworx, entity_profile, remember, get_scoreboard, polymarket_fill_risk, etc. Pairs like remember/recall/forget and subscribe/unsubscribe are consistent, but the broader set mixes verbs, nouns, and prefixes (ask_, pipeworx_, polymarket_, get_, scan_) without a unified scheme.
36 tools is well over the 25-tool 'heavy' threshold, and the set spans multiple unrelated domains: sports data, a general structured-data router, prediction-market analysis, memory storage, and user feedback. Many tools are meta or auxiliary (suggest_questions, pipeworx_feedback, remember/recall/forget) that don't clearly belong to the server's core purpose, making the set feel bloated.
For a sports-data server, core score/news/standings/team/schedule operations exist, but player stats, game details, injuries, and playoff brackets are missing. For the broader Pipeworx data platform the surface is extensive, but the mix of domains makes it hard to declare the set complete for any single stated purpose.