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.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide destructiveHint=true and idempotentHint=true. Description adds 'delete' which matches, but doesn't elaborate on effects or return behavior. Minimal added value beyond 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?
Two sentences, direct and to the point. No redundant information. Every sentence 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?
For a simple tool with one parameter and no output schema, the description covers purpose and usage but omits what the tool returns (e.g., success confirmation). Adequate but could be more complete.
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 the only parameter fully (100% coverage). Description mentions 'by key' but adds no new detail beyond the schema's 'Memory key to delete'.
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?
Description clearly states 'Delete a previously stored memory by key', specifying the verb, resource, and method. References siblings 'remember' and 'recall', providing context on how it fits in the tool family.
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 when to use: 'when context is stale, the task is done, or you want to clear sensitive data'. While it doesn't list when not to use, it pairs with siblings, implying 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.
Each tool has a clearly defined purpose with detailed descriptions, and despite some composite tools, there is no ambiguity in when to use which one.
Tool names mix verb_noun and noun_noun patterns, with some purely verb names, lacking a consistent convention. While readable, the pattern is not predictable.
With 23 tools, the server is on the heavy side for a mixed-purpose toolset. Each tool earns its place, but the count feels slightly bloated for the breadth of domains covered.
The server covers several domains (AI visibility, betting, entity lookup, etc.) with reasonable depth, but the lack of a unified domain means some areas feel under-served (e.g., no update/delete except memory).