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 declare destructiveHint=true and idempotentHint=true. Description clarifies this is a delete operation without adding new behavioral details, but it does add context about pairing with other tools, adding modest 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: first states purpose, second provides usage guidelines. No unnecessary words. 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, no output schema, and relevant annotations, the description is fully sufficient. It covers purpose, usage, and pairing, leaving no gaps.
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?
The input schema has 100% coverage with a single parameter 'key' described as 'Memory key to delete'. The description does not add extra meaning beyond the schema, so baseline 3 is appropriate.
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 starts with 'Delete a previously stored memory by key' which clearly states the action (delete) and resource (memory by key). This directly distinguishes from sibling tools like 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?
Explicitly states use cases: 'Use when context is stale, the task is done, or you want to clear sensitive data the agent saved earlier.' Also mentions pairing with remember and recall, providing clear guidance on 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.
Several tools have overlapping purposes (e.g., ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded; multiple Polymarket tools) and many serve unrelated domains, making it hard for an agent to distinguish which tool to use for a given task, especially given the server's holiday theme.
Most tool names follow a lowercase_with_underscores pattern, but the prefixes vary (ask_pipeworx, pipeworx_*, polymarket_*, etc.) and some names are less descriptive (e.g., process, run, execute-like vague verbs are absent, but still the naming lacks a unified convention across the broad set.
35 tools is excessive for a server named 'Openholidays'. The vast majority of tools (e.g., SEC filings, Polymarket, npm scanning) are unrelated to holidays, making the tool count feel bloated and unfocused.
For the holiday domain, the server includes necessary tools (list_countries, list_subdivisions, public_holidays, school_holidays) and is complete. However, the server's actual scope is far broader, and many unrelated tools are present, which dilutes the completeness for its stated purpose.