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.
Input schema / examplesAdded value: +[
+ {
+ "key": "user_research_topic"
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true and idempotentHint=true. Description adds context about clearing sensitive data and irreversibility, enhancing transparency.
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, front-loaded with purpose, 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?
Low complexity tool with one parameter. Description covers purpose, usage, and pairing. Lacks return value or error info, but not critical given simplicity.
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 clear description of the 'key' parameter. Description does not add meaningful semantics beyond 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?
Clearly states action (Delete) and resource (previously stored memory by key). Differentiates 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 lists when to use (context stale, task done, clear sensitive data) and pairs with related tools (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.
Most tools have clearly distinct purposes (e.g., NPS park tools vs. Pipeworx queries vs. Polymarket analysis). Some overlap exists between ask_pipeworx and ask_pipeworx_grounded, and among the many Polymarket tools, but descriptions help differentiate them.
Naming conventions vary: some use verb_noun (list_parks), others use descriptive phrases (ask_pipeworx_grounded, scan_competitor_ai_presence). While all use snake_case, there is no consistent pattern in prefixes or verb choice.
35 tools is too many for a coherent server. The set appears to bundle multiple unrelated domains (NPS, Pipeworx, Polymarket, memory, subscriptions) into a single server, lacking focused scope.
Each domain has notable gaps (e.g., NPS lacks real-time conditions; Pipeworx lacks data ingestion tools; Polymarket lacks order placement). Some sub-areas (memory, subscriptions) are complete, but overall the surface is incomplete for the broad range of domains.