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 indicate destructiveHint=true and readOnlyHint=false. The description adds that it deletes by key and mentions use cases for clearing sensitive data, providing context beyond annotations. It does not contradict 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?
The description is two sentences, front-loaded with the main purpose. Every sentence adds value: the first states the action, the second gives usage conditions and related tools. No wasted 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?
The tool is simple with one parameter, annotations provided, and no output schema. The description covers the action, usage scenarios, and related tools. It is complete for this simple tool.
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 schema provides a description for the 'key' parameter. The tool description does not add additional parameter details beyond the schema, so the baseline score of 3 applies.
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.' The verb 'delete' and resource 'memory' are specific. It mentions pairing with 'remember' and 'recall' but does not explicitly differentiate from these siblings; however, the purpose is unambiguous.
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 provides explicit contexts: 'when context is stale, the task is done, or you want to clear sensitive data.' It suggests pairing with remember and recall, offering clear guidance. However, it does not specify when not to use the tool.
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 distinct purpose with detailed descriptions. Overlapping areas like polymarket tools are well-differentiated by function (research, arbitrage, edge tracking, fill risk, cross-venue spread). The meta-tools (discover_tools, suggest_questions) further reduce ambiguity.
All tool names use a consistent snake_case pattern (e.g., ask_pipeworx, bet_research, polymarket_edges). The naming is descriptive and predictable, aiding agent selection.
34 tools is on the high side for typical MCP servers. While many are justified by the platform's breadth, the count slightly exceeds the ideal range, potentially overwhelming agents.
The tool set covers a wide array of domains (company data, drugs, prediction markets, economics, news, etc.) with CRUD-like operations for subscriptions and memory. Minor gaps exist (e.g., no direct social media or custom API tool), but overall the surface is well-matched to the server's data platform purpose.