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 confirms 'Delete' but adds no additional behavioral context beyond that.
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, no wasted words. The purpose and usage are front-loaded and clear.
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?
Simple tool with one parameter and no output schema. The description covers action, when to use, and sibling tools. No gaps for a memory deletion function.
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?
Single parameter 'key' is documented in the schema with 'Memory key to delete'. The description mentions 'by key' but adds no extra meaning beyond schema coverage of 100%.
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' – a specific verb and resource. It distinguishes itself by mentioning 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?
Provides explicit scenarios: 'Use when context is stale, the task is done, or you want to clear sensitive data.' Lacks explicit when-not-to-use but still strong guidance.
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 tool set mixes tools from multiple unrelated domains (HathiTrust, Pipeworx data platform, Polymarket, npm, etc.), making it unclear which tool to use for a given task. Overlap exists between ask_pipeworx and ask_pipeworx_grounded, and between several Polymarket tools, while the HathiTrust-specific tools are few and buried among many others, causing confusion.
Naming conventions are inconsistent across the tool set. Some tools use verb_noun (check_full_view, lookup_by_identifier), others use noun_verb (entity_profile, deep_research), and some are single verbs (forget, remember, subscribe). There is no predictable pattern, making it harder for an agent to guess tool names.
With 33 tools, the count is high, but only 3 (get_record, lookup_by_identifier, check_full_view) are relevant to the server's stated purpose (HathiTrust). The remaining 30 tools appear to be from unrelated domains (Pipeworx data platform, Polymarket, npm, etc.), making the tool count severely mismatched with the server name.
For the HathiTrust domain, the tool surface is severely incomplete: only three basic lookup tools with no search, browse, or management capabilities. The broader set includes tools for many other domains, but that does not compensate for the lack of coverage of the server's primary purpose.