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=true and idempotentHint=true, so the safety profile is known. The description adds that it deletes a memory and mentions clearing sensitive data, but does not disclose additional behaviors like irreversibility or error handling.
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, front-loaded with the action, no superfluous text.
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 single-parameter tool with strong annotations, the description covers purpose, usage, and related tools. It doesn't describe return values, but delete operations typically have no meaningful output.
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 covers the only parameter key with a description 'Memory key to delete', so 100% coverage. The description mentions 'by key' but adds no additional formatting or 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 clearly states the action 'Delete a previously stored memory by key' with a specific verb and resource. It distinguishes from sibling tools like remember and recall by focusing on 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 the agent saved earlier.' Also points to related tools remember and recall, providing alternative context.
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.
Many tools have overlapping purposes, such as ask_pipeworx, ask_pipeworx_grounded, deep_research, and also multiple Polymarket tools (bet_research, polymarket_edges, polymarket_arbitrage). Descriptions try to differentiate but the boundaries are unclear, causing confusion.
Naming conventions are mixed: some use snake_case (ask_pipeworx, query_layer), some use descriptive phrases (entity_profile, recent_changes), and there is no consistent verb_noun pattern. The variety makes it hard to predict tool names.
33 tools is far too many for a server named 'Arcgis Fairfield', as most tools are unrelated to GIS or Fairfield (e.g., npm dependency checks, prediction markets, AI visibility). The tool count severely mismatches the server's purported scope.
The server's stated purpose is ArcGIS Fairfield, but only 3 tools (layer_info, query_layer, search_datasets) relate to that domain. Critical GIS operations like updating features or managing services are missing, while the vast majority of tools are for other domains.