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 adds context about clearing sensitive data but doesn't elaborate on irreversible nature or other side effects. No contradiction.
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, front-loaded with the action.
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?
Complete for a simple delete tool with one parameter, no output schema, and good annotations. Includes usage guidance and sibling tool pairing.
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 'key' parameter already described as 'Memory key to delete'. Description adds no additional meaning 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?
Clear verb 'Delete' and resource 'memory by key'. Distinguishes from 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?
Explicitly states when to use (stale context, task done, clear sensitive data) and references sibling tools, but does not explicitly state when not to use.
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.
Multiple tool clusters have overlapping functions: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are nearly interchangeable, deep_research overlaps with the ask_pipeworx family, and the six Polymarket tools all analyze the same domain with subtle differences. discover_tools and suggest_questions also both serve as discovery entry points, making it difficult for an agent to confidently select the correct tool.
All names are snake_case, but there is no uniform structural pattern. Verb_object names like format_currency and resolve_entity coexist with noun_phrases like entity_profile and polymarket_arbitrage, bare verbs like remember and forget, and adjective_noun forms like recent_alerts. Cluster-specific prefixes are consistent, but the overall convention is mixed.
With 33 tools, the set is substantially over-scoped and exceeds the suggested 3-15 range. Many tools could be consolidated, such as the three ask_pipeworx variants, the six Polymarket tools, and the two formatting utilities. The broad domain justifies some size, but the count feels inflated and will burden agents with excessive choice.
The server covers many areas thoroughly: memory has remember/recall/forget, subscriptions have subscribe/unsubscribe/list/recent_alerts, and research tools span lookup, profiling, comparison, and verification. However, there are notable gaps: pipeworx:// citation URIs are returned but no tool explicitly fetches or reads a record by URI, and there is no direct way to manage account-level settings beyond memory. These missing operations force agents to work around limitations.