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 and idempotentHint. The description adds context about clearing sensitive data but doesn't disclose additional behavioral details like irreversibility or behavior on missing keys; it doesn't contradict annotations.
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 are front-loaded with the core action, then usage guidance; every word earns its place.
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 one-parameter delete tool with strong annotations and no output schema, the description adequately covers core function, usage timing, and relation to sibling tools. Minor gap: no mention of non-existent key behavior, but idempotentHint covers that implicitly.
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 description coverage is 100% for the single key parameter, and the description merely says 'by key' without adding format or lifecycle details, so it adds no extra 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?
The description opens with 'Delete a previously stored memory by key,' using a specific verb and resource that clearly distinguishes it 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?
Provides explicit use cases (stale context, task done, sensitive data) and suggests pairing with remember and recall, but doesn't explicitly state when not to use it.
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.
Descriptions are unusually explicit about when to use each tool (single lookup vs grounded vs deep research), but the set still contains several genuinely overlapping tools: ask_pipeworx_beta is explicitly identical to ask_pipeworx, scan_competitor_ai_presence wraps ai_visibility, and six polymarket_* tools share the same 'edge/arbitrage' conceptual space. An agent can usually pick the right tool but faces real ambiguity in several clusters.
Names are uniformly snake_case and readable, and there are coherent prefix families (ask_pipeworx_*, polymarket_*, pipeworx_*). However the verb placement is inconsistent: verb_noun (ask_pipeworx, validate_claim, discover_tools) coexists with noun-first names (recent_changes, entity_compare, layer_info, polymarket_edges), and bet_research sits outside the polymarket_* family despite being a prediction-market tool.
34 tools is well past the 'feels heavy' threshold, and more importantly the set mixes what looks like three different servers: a tiny ArcGIS/Longview GIS slice (layer_info, query_layer, search_datasets), a massive general-purpose data-research platform from Pipeworx, and a Polymarket prediction-market toolkit. Most tools earn their place for the platform, but far too few belong to the named domain.
The research surface is remarkably complete: a router, grounded and beta variants, deep multi-source research, claim verification, entity/profile/change resolution, discovery and suggestion helpers, memory (remember/recall/forget), subscriptions (subscribe/unsubscribe/recent_alerts), and feedback — no obvious lifecycle dead ends. Minute gaps exist on the GIS side (no dataset editing, no metadata browsing, no named export/view ops) and a few nooks like screen- leisure tools have no progress/status endpoints, but these are workaroundable.