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 indicate destructiveHint=true. The description adds context (clearing sensitive data, stale context) but does not reveal additional behavioral traits beyond what is implied by 'delete'.
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 succinct sentences with no wasted words. Purpose and usage are front-loaded.
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?
With one parameter, full schema coverage, annotations, and sibling links, the description is complete. It covers what, when, and relations.
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 has 100% coverage with parameter description 'Memory key to delete'. The description does not add extra 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?
The description clearly states the action ('Delete') and the resource ('previously stored memory by key'). It distinguishes itself from sibling tools 'remember' and 'recall' by specifying deletion.
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: 'when context is stale, the task is done, or you want to clear sensitive data'. Also advises pairing with siblings, implying 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.
Several clusters of tools have unclear boundaries: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, validate_claim, and bet_research all overlap as query/research entry points, and ai_visibility_check vs. scan_competitor_ai_presence plus the six polymarket_* tools create further confusion. An agent would often need deep description reading to pick the right tool.
Naming mixes consistent verb_noun forms (get_aircraft, resolve_entity, validate_claim) with noun phrases (aircraft_near, military_aircraft, recent_alerts), adjective-led names (polymarket_arbitrage), and conversational names (ask_pipeworx, suggest_questions). Subgroups like polymarket_* are internally consistent, but overall there is no unified pattern.
35 tools is high for any cohesive server, especially one named 'Adsb' where only 4 tools relate to aircraft tracking. The count is inflated by many overlapping meta-research, prediction-market, memory, and subscription tools, making it feel like several servers were merged into one.
For the implied 'Adsb' domain, only live ADSB positioning is covered; airport info, flight schedules, route search, and aviation weather are missing. Even as a general data/betting server, there are gaps like a direct stock-quote tool and unclear lifecycle coverage across the mixed feature set, so agents will likely hit dead ends.