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?
Descriptive text just says 'Delete', which aligns with annotations (destructiveHint=true). No additional behavioral context beyond what annotations provide.
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?
Extremely concise: two sentences that efficiently convey purpose, usage guidance, and sibling context without waste.
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?
All necessary information for a simple deletion tool (one param, no output schema) is present: what it does, when to use, and with what 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 schema already describes the 'key' parameter. Description adds no extra meaning beyond the schema.
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' with a specific verb and resource, and implicitly distinguishes from sibling tools '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?
Explicit guidance on when to use: context stale, task done, or clearing sensitive data. Also suggests pairing with 'remember' and 'recall'.
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 set is dominated by overlapping Pipeworx and prediction-market tools, with ask_pipeworx and ask_pipeworx_beta explicitly described as currently identical, and ask_pipeworx_grounded, deep_research, and discover_tools serving heavily overlapping lookup purposes. The four Microsoft To Do tools are buried among 31 unrelated tools, making it very hard for an agent to select the right tool for the server's apparent domain.
Most names are snake_case, but the naming conventions are otherwise mixed: there are verb_noun tools like list_tasks and get_task, bare verbs like remember/forget/recall, prefixed families like polymarket_*, and noun-phrase names like entity_profile, recent_changes, and pipeworx_trending. The lack of a consistent pattern across the set, especially relative to the Microsoft To Do server name, makes naming unpredictable.
35 tools is already heavy, but the bigger problem is that only 4 of them are for Microsoft To Do, the server's stated name and purpose. The remaining 31 tools belong to unrelated Pipeworx data, prediction-market, and memory-management domains, which is an extreme scope mismatch.
For a Microsoft To Do server, the surface is severely incomplete: list_task_lists, list_tasks, get_task, and find_due_tasks cover reading and browsing only, with no create, update, complete, or delete operations. Even the broader Pipeworx functionality is scattered and redundant rather than forming a coherent domain surface.