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. The description adds context about use cases but does not contradict annotations. No additional behavioral details beyond what annotations convey.
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 with no fluff. The purpose is front-loaded, followed by usage guidelines. Every sentence adds value.
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 simplicity of the tool (1 param, no output schema), the description is complete. It covers purpose, usage context, and pairing with siblings.
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 coverage is 100%, and the description does not add any parameter-level details beyond the schema's 'key' description. Baseline score is appropriate as schema does the heavy lifting.
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 distinguishes from siblings by mentioning pairing with 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?
Provides explicit when-to-use scenarios: stale context, task done, clearing sensitive data. Mentions pairing with siblings. Lacks explicit exclusions or alternatives, but the guidance is sufficient.
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.
Many tools overlap in purpose, such as the multiple Polymarket tools (bet_research, polymarket_arbitrage, polymarket_edges, etc.) and the several query tools (ask_pipeworx, ask_pipeworx_grounded, deep_research). Memory tools (remember, recall, forget) also add to the confusion.
Tool names are mostly snake_case but vary in pattern: some are verb_noun (add_duration, compare_entities), others are noun_noun (entity_profile, date_diff) or single verbs (forget). This mix reduces predictability but is not chaotic.
The server name 'Datecalc' implies a narrow focus, yet 33 tools exist covering far more than date calculations. The count is too high for the implied purpose, and many tools are unrelated to the server's apparent domain.
For the implied date calculation domain, only three tools exist (add_duration, date_diff, date_info), leaving obvious gaps. For the actual broad data access domain, coverage is better but still lacks a cohesive structure.