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 confirms the destructive nature (delete) but adds no further behavioral details beyond what annotations indicate. No contradiction.
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 (three sentences), front-loaded with the core action, and every sentence adds value—no filler 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 tool with one parameter and no output schema, the description provides complete context: what it does, when to use it, and how it relates to siblings. Annotations cover the rest.
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%, so the schema fully documents the 'key' parameter. The description does not add additional meaning beyond the schema's 'Memory key to delete', so baseline 3 applies.
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 clearly states the action 'Delete' and the resource 'previously stored memory by key', distinguishing it from sibling tools like 'remember' and 'recall' which store and retrieve memories 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?
Explicit usage guidance is provided: 'Use when context is stale, the task is done, or you want to clear sensitive data'. It also suggests pairing with 'remember' and 'recall', effectively directing the agent on when to use this tool versus alternatives.
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.
Multiple tools share overlapping purposes: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical variants, and the five polymarket_* tools cover heavily overlapping territory. An agent must read lengthy descriptions to distinguish between them, and pairs like validate_claim vs ask_pipeworx_grounded or discover_tools vs suggest_questions have fuzzy boundaries.
Naming is wildly inconsistent: verb_noun (compare_entities, discover_tools), bare verbs (forget, remember, subscribe), noun phrases (entity_profile, recent_alerts, pipeworx_feedback), prefixed families (tradier_*, polymarket_*) and suffixed variants (ask_pipeworx_beta, ask_pipeworx_grounded). There is no single predictable convention across the set.
34 tools is far beyond the 15-25 heavy range, and the count is inflated by near-duplicates like ask_pipeworx/ask_pipeworx_beta and five polymarket edge tools. The server mixes several unrelated domains (Tradier quotes/options, Pipeworx research, Polymarket analysis, memory, subscriptions, web utilities), making the scope feel unbounded.
For a server named Tradier, having only quote and option-chain endpoints is a significant gap—no historical data, account, positions, or order execution. The Pipeworx/Polymarket side is more complete, but the inclusion of unrelated utilities like generate_llms_txt and scan_dependency means no single domain is fully served.