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 provide destructiveHint=true and idempotentHint=true. The description aligns with these but doesn't add new behavioral details such as irreversibility, no-op behavior for missing keys, or return format. It does clarify the scope of previously stored memories.
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?
Two sentences, front-loaded with the action, then usage guidance. 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?
For a simple one-parameter deletion tool with annotations covering destructive and idempotent hints, the description adequately covers purpose, usage, and pairing. Missing return value behavior, but no output schema exists and this is a simple tool.
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 covers 100% of parameters, with the key property described as 'Memory key to delete'. The description reinforces 'by key' but adds no additional format or semantic details 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?
The description uses the specific verb 'Delete' with the resource 'previously stored memory' and method 'by key'. This clearly distinguishes from sibling tools like 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 three use cases: stale context, task done, clearing sensitive data. It also suggests pairing with remember and recall, giving complementary tool context. However, it doesn't state when not to use or mention alternative tools by name.
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.
Heavy overlap within the ask_pipeworx family (ask_pipeworx, ask_pipeworx_beta which is currently identical, ask_pipeworx_grounded, deep_research) and among prediction market tools (polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread) makes selection genuinely ambiguous. Some tools are distinct (remember/recall/forget), but the clustering blurs boundaries.
Conventions are mixed: some tools use verb_noun (list_games, get_game, filter_games, subscribe, unsubscribe, recall, remember) while others use ad-hoc noun phrases or brand-style names (polymarket_arbitrage, entity_profile, deep_research, ask_pipeworx, bet_research). No single pattern dominates, making it harder to predict tool names.
34 tools is heavy, and the mismatch is severe: the server is named 'videogames' but only 3 of 34 tools (list_games, get_game, filter_games) have any relation to video games. The bulk are Pipeworx data/prediction-market/memory utilities that do not belong under this server's apparent purpose. This is a fundamental scope failure.
As a video game server, the surface is extremely thin: only list/get/filter by tags and platform, with no search by name, no CRUD, no reviews, no categories beyond the fixed filter set. The other 31 tools are irrelevant to the videogames domain, so the stated purpose is largely uncovered. The mismatch makes coverage assessment nearly impossible for the actual server name.