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, so the description adds little beyond those. It mentions clearing sensitive data, but no further behavioral traits are disclosed.
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 the core 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?
For a simple, one-parameter, no-output-schema tool with informative annotations, the description is complete enough.
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 description only repeats the parameter name 'key' without adding meaning beyond what the schema provides.
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' using a specific verb and resource. It differentiates from sibling tools by explicitly pairing with 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 when-to-use scenarios (stale context, task done, clear sensitive data) and mentions pairing with remember and recall, offering 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.
Most tools have distinct purposes, but there is some overlap (e.g., ai_visibility_check and scan_competitor_ai_presence are related; memory tools remember/recall/forget form a clear subgroup). Descriptions are detailed enough to differentiate, but the broad scope may cause occasional mis-selection.
Naming is inconsistent: some tools use verb_noun (list_accounts, get_profit_and_loss), others are single words (forget, recall), and some use snake_case with mixed verbs (ai_visibility_check, ask_pipeworx, bet_research). No uniform pattern makes the set harder to navigate.
25 tools is high but not extreme given the broad scope (accounting, betting, data queries, npm, memory, etc.). However, the server tries to cover too many domains, making it feel bloated. Each tool is individually useful, but the count is borderline excessive for coherence.
The Xero accounting subset is incomplete: only list and get operations, no create/update/delete for invoices, contacts, or accounts. Other domains (betting, npm) are covered well, but the core accounting purpose has significant gaps that will hinder agents.