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.
Input schema / examplesAdded value: +[
+ {
+ "key": "user_research_topic"
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint and idempotentHint, so the description's 'Delete' wording aligns without contradiction. No additional behavioral context (e.g., permanence, side effects) is provided beyond the annotations, but the risk profile is fully captured by the annotations.
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 three short sentences: the action, the usage guidance, and the sibling pairing. It is front-loaded and contains no fluff.
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 delete tool with comprehensive annotations, the description covers purpose, usage, and sibling relationships. No output schema is needed, and the risk profile is fully annotated.
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 schema provides a full description of the single 'key' parameter as 'Memory key to delete' (100% coverage). The description adds the qualifier 'previously stored' and 'by key' but no new format or semantic details beyond the schema baseline.
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 opens with a specific verb ('Delete') and resource ('memory by key'), clearly distinguishing it from sibling memory tools like 'remember' and 'recall'. It states exactly what the tool does without ambiguity.
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?
It explicitly says when to use the tool: 'when context is stale, the task is done, or you want to clear sensitive data the agent saved earlier.' It also recommends pairing with 'remember and recall,' providing guidance on related tools.
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.
The StackExchange tools are distinct, but the dominating data-lookup cluster is highly ambiguous: ask_pipeworx, ask_pipeworx_beta (explicitly identical today), ask_pipeworx_grounded, deep_research, and validate_claim all route into the same underlying tool catalog. The polymorpharket tools also overlap heavily, making selection between bet_research, polymarket_edges, polymarket_arbitrage, and fill-risk checks genuinely hard.
The names are all snake_case but otherwise follow no consistent pattern: bare verbs (remember, forget, subscribe), prefixed names (pipeworx_feedback, stack_get_user), composite domain names (ask_pipeworx, generate_llms_txt), and generic verbs (resolve_entity, validate_claim, search_within). The StackExchange subset itself is split between stack_get_user/stack_tags and search_questions/get_answers.
36 tools is already in the 'too many' range for one server, and the mismatch with the server name is severe: only 5 of 36 tools relate to StackExchange. The rest form a broad Pipeworx/prediction-market data platform that would itself be oversized for a focused purpose.
For a StackExchange-focused server, the surface has core read operations but lacks question-detail-by-ID, comments, related questions, or any write/community actions, and the 31 unrelated tools do not fill that gap. For the broader apparent Pipeworx platform coverage is broad, but the set has no single coherent domain against which completeness can be meaningfully judged.