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 |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true and idempotentHint=true, so the description's 'Delete' is consistent. It adds use-case context (clearing sensitive data) but does not disclose extra behavioral traits like error handling or permanence beyond what the annotations imply. 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?
The description is two sentences long, front-loaded with the core action, and free of unnecessary details. Every clause adds value: the first states the operation, the second gives usage context and sibling tool references.
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 delete tool with good annotations and schema coverage, the description is nearly complete. It covers the operation, usage triggers, and relationship to related tools. It could mention what happens if the key is missing or whether deletion is permanent, but this is minor given the tool's simplicity.
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?
The input schema already documents the 'key' parameter with 'Memory key to delete' at 100% coverage. The description adds no additional parameter-specific meaning, only restating the deletion action. This is the baseline expected score when schema covers all parameters.
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 tool's function: 'Delete a previously stored memory by key.' It uses a specific verb (delete) + resource (memory) and distinguishes it from sibling tools like remember and recall by explicitly contrasting deletion with storage/retrieval.
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?
The description provides explicit when-to-use guidance: 'Use when context is stale, the task is done, or you want to clear sensitive data the agent saved earlier.' It also references alternatives by saying 'Pair with remember and recall,' making the use case clear.
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 tool groups overlap heavily: the three ask_pipeworx variants (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) differ mainly in guarantees, and six Polymarket tools (bet_research, polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread) all target the same trading-concept space with fuzzy boundaries. While ArcGIS, memory, and subscription tools are distinct, an agent will frequently struggle to pick the right research or analysis tool.
All names are snake_case, but the structural pattern is inconsistent. Some are verb-first (query_layer, search_datasets, validate_claim), others are noun-first or domain-prefixed (entity_profile, layer_info, polymarket_edges, recent_alerts, pipeworx_feedback). There is no predictable verb_noun convention across the set, making it hard to guess a tool's name from its function.
At 34 tools, the set is well above the typical focused-server range, and the server name 'Arcgis Eagan' suggests a narrow GIS purpose while only 3–4 tools are actually ArcGIS-related. The remaining ~30 tools form a broad, unrelated utility collection (Pipeworx data, memory, subscriptions, trending, npm scanning), making the count feel bloated and unfocused.
For the primary ArcGIS domain, only search, layer inspection, and querying are supported — there are no create, update, delete, or editing tools, leaving obvious lifecycle gaps. Meanwhile, the Pipeworx side is over-stocked with redundant analysis tools, and the overall mix lacks a coherent coverage story for any single stated purpose.