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 doesn't need to restate that. It adds minor context about clearing 'sensitive data the agent saved earlier', which reinforces the safety implication, but otherwise relies on annotations. No contradiction; score 3 is appropriate as the description adds some value beyond 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, zero fluff. The first sentence is a direct action statement; the second provides usage context and sibling references. Every phrase earns its place, and the description is immediately understandable.
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-by-key tool with one required parameter and no output schema, the description is complete. Annotations cover safety (destructive, idempotent), and the description provides usage context. It could mention idempotency behavior explicitly, but annotations already cover that, so this is sufficient.
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 fully documents the single parameter 'key' with description 'Memory key to delete' (100% coverage). The description does not add additional parameter semantics beyond what the schema provides, so baseline 3 is warranted. The example in the schema further clarifies usage.
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', making the action specific and unambiguous. It also distinguishes itself from sibling tools by explicitly naming 'remember' and 'recall', showing it is the complementary deletion operation.
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 guidance: 'when context is stale, the task is done, or you want to clear sensitive data'. It also mentions pairing with 'remember and recall', giving context on how it fits into the memory workflow, which helps the agent select it over alternatives.
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 tools overlap heavily: ask_pipeworx and ask_pipeworx_beta are explicitly identical, and ask_pipeworx, ask_pipeworx_grounded, deep_research, discover_tools, and suggest_questions all serve as query/discovery entry points. Polymarket tools also blur together (bet_research, polymarket_edges, polymarket_arbitrage, polymarket_edge_tracker, polymarket_fill_risk). While many tools have distinct purposes, these overlapping clusters create real misselection risk.
All names are snake_case but the pattern is inconsistent: some are verb_noun (ask_pipeworx, search_datasets, validate_claim), some are noun_verb (query_layer, layer_info is noun_noun), and some are single vague words (forget, recall, remember). No consistent verb_prefix or resource_suffix convention, and the mix of meta-tools vs data tools makes the naming feel arbitrary.
34 tools is far too many for a server ostensibly named 'Arcgis Lancaster' — only 3 tools relate to GIS. The bulk is an unrelated general-purpose data/prediction-market toolkit, making the count excessive for the apparent scope. Even as a broad data toolset, 34 tools is on the heavy side and would benefit from splitting into focused servers.
The tool surface is a grab bag with no coherent domain, so completeness is hard to assess and clearly lopsided. GIS functionality has search/query/info but no lifecycle management, while the data side has many query/analysis tools but no create/update/delete operations except for subscriptions and memory. Obvious gaps exist for a 'Lancaster' server (e.g., no layer creation, editing, or spatial analysis tools), and the unrelated tools make the set feel incomplete for any single stated purpose.