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=true and idempotentHint=true, so the destructive nature is known. The description adds context about clearing sensitive data and that the memory was previously stored, but does not disclose additional behaviors like irreversibility or error handling. With annotations present, this is acceptable but not rich.
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 and followed by usage guidance. Every word earns its place.
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?
This is a simple tool with one parameter, no output schema, and strong annotations. The description covers purpose, usage timing, and relationship to paired tools. Given the low complexity, it is complete enough.
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 description coverage is 100%, so the schema already documents the 'key' parameter. The description only repeats that deletion is by key, adding no additional semantic meaning beyond what the schema provides. 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 clearly states the tool deletes a previously stored memory by key, using a specific verb and resource. It distinguishes itself from sibling tools like remember and recall by positioning as the deletion counterpart.
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?
Provides explicit use cases: when context is stale, the task is done, or to clear sensitive data. It also mentions pairing with remember and recall, though it does not explicitly state when not to use the tool.
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 ask_pipeworx family (ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research) has significant boundary blurring—ask_pipeworx_beta explicitly 'currently matches ask_pipeworx exactly'—and the six prediction-market tools (bet_research, polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread) have heavily overlapping edge-detection purposes. Only the archive, memory, and subscription families are cleanly delineated.
There are consistent family prefixes (ask_*, polymarket_*, pipeworx_*) and clean pluralized lists (list_files, list_subscriptions), but the full set mixes bare verbs (remember, recall, forget, search), nouns (entity_profile), and varying patterns (bet_research vs compare_entities, search vs search_within vs recent_changes). Readable in clusters, but no single naming convention binds the set.
35 tools is heavy, and the count is fattened by five distinct product areas—data routing, prediction markets, archive.org access, memory, and subscriptions—that have little to do with each other or with the server name 'archive'. It sits in the 25+ heavy zone even before honoring the mismatch between its name and the sprawl of its purpose.
Individual subdomains are well-covered: the memory trio (remember/recall/forget), subscription lifecycle (subscribe/unsubscribe/list_subscriptions/recent_alerts), and archive lineup (search/get_metadata/list_files/wayback_check) are each complete, and extra machinery like pipeworx_feedback and recent_changes shows domain care. But the unifying domain is incoherent—a server named 'archive' that's also a universal data router and prediction-market toolkit—and the scope ends up both bloated and still full of gaps for any one of the intended users (e.g. no archive-item upload, no prediction-market portfolio management).