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, covering the destructive and idempotent nature. The description adds context about 'previously stored' and 'sensitive data', but does not go beyond annotations to describe side effects or error behavior. No contradiction found.
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 two sentences, front-loaded with the action, includes usage guidance, and mentions sibling tools. Every sentence serves a purpose with no filler or redundancy.
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 single-parameter destructive tool with annotations covering idempotency and destructiveness, this description is complete. It tells the agent what the tool does, when to use it, and how it relates to remember and recall, without needing to explain return values (no output schema).
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 fully describes the single 'key' parameter with 'Memory key to delete' (100% coverage). The description reinforces that deletion happens 'by key' but adds little new meaning beyond the schema, 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 'Delete a previously stored memory by key', using a specific verb and resource. It effectively distinguishes itself from sibling tools like remember and recall by naming them as complements.
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 when-to-use scenarios: 'context is stale, the task is done, or you want to clear sensitive data'. It also names remember and recall as associated tools, but lacks explicit when-not-to-use guidance or direct comparison to alternatives.
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 have overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded are highly similar; deep_research also overlaps with ask_pipeworx. This makes it hard for an agent to distinguish which to use.
Tool names are inconsistent, mixing camelCase (ask_pipeworx, ai_visibility_check) with snake_case (deep_research, compare_entities). Some are verb phrases, others are nouns (groups, tags), with no unified pattern.
With 36 tools covering EU open data, general data retrieval (Pipeworx), and prediction markets (Polymarket), the count is too high for a coherent, focused server. Many tools are redundant or meta-tools.
For a server named 'Data Europa', the EU open-data tools are basic (search, package, groups) lacking update/delete or analysis. The additional Pipeworx/Polymarket tools are extensive but unrelated, making the overall surface incomplete for the implied domain.