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 |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate destructiveHint=true and idempotentHint=true. Description adds context about clearing sensitive data but doesn't elaborate on side effects or recovery.
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?
Three focused sentences: action, usage guidance, and sibling references. No unnecessary words.
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?
Single-parameter tool fully described with purpose, usage, and annotations. No missing details for agent decision-making.
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 parameter description is minimal ('Memory key to delete'). Description does not add meaning beyond the schema.
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?
Description uses specific verb 'delete' and resource 'memory', clearly distinguishing from siblings 'remember' and 'recall'.
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?
Explicitly states when to use (stale context, task done, clear sensitive data) and pairs with alternatives ('remember', 'recall').
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 or intentionally duplicated purposes: ask_pipeworx/ask_pipeworx_beta currently behave identically, and the Polymarket cluster (bet_research, polymarket_arbitrage, polymarket_edges, polymarket_fill_risk, polymarket_kalshi_spread) presents multiple scanners with fuzzy boundaries. The long descriptions help, but the set as a whole is hard to navigate without close reading.
Naming is a mix of bare single nouns (hero, match, meta, remember, forget), snake_case verb-first names (ask_pipeworx, compare_entities, generate_llms_txt), and noun-first compounds (pipeworx_feedback, bet_research, scan_competitor_ai_presence). There is no consistent verb_noun or noun-verb convention across the set.
At 43 tools, the server bundles at least five unrelated domains (Dota 2 stats, Pipeworx data querying, Polymarket analytics, memory, subscriptions, AI visibility). That is far too many for a focused MCP server, and the mix makes the surface feel like a grab bag rather than a purpose-built toolkit.
Each subdomain individually has solid coverage: Dota 2 has heroes/matches/players/tournaments/meta plus a GraphQL fallback, the data layer has discovery + routing + grounding + validation, and memory/subscriptions have full lifecycle operations. The only real gap is cohesion across domains; within each slice there are no obvious dead ends.