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. Description adds context about clearing sensitive data but doesn't disclose additional behavioral traits beyond what annotations provide.
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 concise sentences with no wasted words. The purpose is front-loaded, and usage guidelines follow immediately.
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 delete with one required parameter, the description covers purpose, usage, and context. Annotations cover destructive behavior, so no gaps.
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 a clear description of 'key' as 'Memory key to delete'. Description adds no 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 verb 'Delete' and resource 'previously stored memory by key'. It distinguishes from siblings by explicitly mentioning '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 completion, clearing sensitive data. Also pairs with alternative 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.
Multiple tools are near-duplicates or strongly overlapping: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are only mode/version variants, and discover_tools overlaps with suggest_questions, ai_visibility_check with scan_competitor_ai_presence, and the Polymarket tools with each other. An agent would frequently need a deep read of the descriptions to know which one is truly appropriate.
The naming is almost entirely snake_case and mostly follows a verb_noun or domain_noun pattern, e.g. query_layer, list_subscriptions, resolve_entity, compare_entities. Minor deviations like entity_profile, pipeworx_feedback, and polymarket_arbitrage are noun-first, but the overall pattern is still recognizable and predictable.
34 tools for a server branded 'Arcgis Tallahassee' is far too many, especially since only a handful of them are GIS-related. The rest constitute a large general-purpose Pipeworx data platform, which at this tool count becomes unwieldy and will increase an agent's selection failure rate.
The core read-only GIS flow is covered (search_datasets → layer_info → query_layer), and the Pipeworx side is broad. However, there are notable gaps: no ArcGIS service management, no layer/feature editing, no spatial operations, and no deeper GIS functions. Because the server's stated purpose is ArcGIS-focused, the overall surface is only partially complete relative to that domain.