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 indicate destructiveHint=true and idempotentHint=true. The description adds context about clearing sensitive data, which goes beyond the annotations. No contradictions.
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 consists of two concise sentences. The first sentence states the purpose, and the second provides usage guidelines. 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?
Given the tool has one required parameter fully described by the schema, and annotations cover behavioral traits, the description is complete. It explains when to use and what the tool does. No output schema is needed.
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 single parameter 'key' is fully documented in the input schema with description 'Memory key to delete'. The description does not add new semantic information beyond what the schema provides, so 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 verb 'Delete', the resource 'previously stored memory', and the method 'by key'. It also distinguishes from sibling tools 'remember' and 'recall' by mentioning pairing.
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?
The description explicitly provides usage conditions: 'when context is stale, the task is done, or you want to clear sensitive data'. It also pairs with 'remember' and 'recall' for context.
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 overlap heavily: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all route natural-language questions to the same underlying data catalog, and the polymarket_* family has several near-synonymous scanning tools. Entity_profile, compare_entities, and recent_changes also have fuzzy boundaries. Only the three cat tools are clearly distinct, but an agent could easily pick the wrong tool across the Pipeworx family.
The names are consistently snake_case and several families share clear prefixes like ask_pipeworx, polymarket_, and list_. However, the set mixes imperative verb-first names with noun-style names, and the cat_* tools do not share any naming pattern with the dominant Pipeworx family.
34 tools is too many for a server named Cataas, and only 3 of them are actually cat-related. The other 31 tools belong to an unrelated data-research and prediction-market platform, making the tool count inappropriate for the apparent purpose.
As a cat-image server, the surface is thin: random_cat, cat_by_tag, and list_tags cover basics but omit common Cataas operations like GIFs or text-on-cat. As a data-research platform, the cat tools are noise, so the mixed set is incomplete and incoherent for either apparent purpose.