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 convey destructiveHint=true and idempotentHint=true. The description adds no new behavioral traits beyond restating the delete action, but it aligns with annotations without 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?
Two concise sentences, no wasted words. First sentence states action, second provides usage guidance. Efficient and well-structured.
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 full schema coverage and annotations, the description covers purpose and usage completely. No output schema needed.
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 'Memory key to delete'. The description's 'by key' adds no additional semantic value 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 states 'Delete a previously stored memory by key' with a specific verb and resource. It distinguishes itself from siblings 'remember' and 'recall', making the purpose clear.
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 context for use: when context is stale, task done, or clearing sensitive data. It also mentions pairing with siblings, though it lacks explicit when-not-to-use guidance.
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, e.g., ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded all answer questions; polymarket_edges and polymarket_arbitrage both find opportunities; and memory tools (remember, recall, forget) are separate but simple. This makes it hard for an agent to pick the right tool without careful reading.
Naming is inconsistent: some tools use verb_noun (generate_llms_txt, discover_tools), others noun_noun (entity_profile, amtrak_station_info), and some are single verbs (remember, forget). The Amtrak tools follow a pattern but the rest do not, leading to a chaotic mix.
With 35 tools but only 4 actually related to Amtrak, the server is severely over-scoped for its stated purpose. The majority of tools are unrelated, making it feel bloated and misnamed.
For an Amtrak server, the tool surface is severely incomplete: lacks booking, schedules, ticket info, delay details beyond worst delay, and station amenities. The tiny Amtrak subset is a mere fraction of what users would expect.