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 confirms deletion but adds no 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?
Two concise sentences, front-loaded with action, 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?
Simple tool with one parameter and no output schema; description fully covers purpose, usage, and parameter meaning.
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% with parameter 'key' described as 'Memory key to delete'. Description adds no additional semantics 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 states 'Delete a previously stored memory by key' with a specific verb and resource, and distinguishes from siblings by mentioning '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 when to use it: 'when context is stale, the task is done, or you want to clear sensitive data'. Also mentions pairing with siblings for context.
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.
Most tools have distinct purposes with clear descriptions, but ask_pipeworx_beta is nearly identical to ask_pipeworx, and the presence of several meta-tools may cause slight confusion. Overall, an agent can differentiate most tools.
Tool names consistently use lowercase_with_underscores and follow an action_domain pattern (e.g., validate_claim, scan_competitor_ai_presence). There is a mix of verb-noun and noun-verb, but the pattern is predictable and readable.
33 tools is on the higher end, but given the broad scope (finance, drugs, prediction markets, data retrieval, memory), the count is reasonable. However, the server name 'Hurricanes' suggests a narrower focus, making the count feel excessive for that domain.
The tool set covers a wide range of data domains and includes meta-tools for discovery, grounded answers, and subscriptions. Minor gaps exist (e.g., no non-US company data), but overall the surface is comprehensive for a general-purpose data server.