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 readOnlyHint=false, so the description's 'Delete' aligns. The description adds context about clearing sensitive data, but not much else beyond what annotations provide. With annotations carrying the safety profile, a 3 is appropriate.
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, no redundancy. The first sentence immediately states action and resource, the second provides usage guidance. Every word earns its place.
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 no output schema and strong annotations, the description covers purpose, usage, and behavioral context adequately. Nothing is missing.
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 single 'key' parameter described as 'Memory key to delete'. The description adds 'previously stored' but does not elaborate on format or constraints. Baseline 3 applies as schema handles the burden.
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 purpose: deleting a previously stored memory by key. It uses specific verb ('delete') and resource ('memory by key'), and the pairing hint with 'remember' and 'recall' distinguishes it from sibling tools.
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 explicitly lists when to use (stale context, task done, clear sensitive data) and hints at pairing with siblings. It does not explicitly state when not to use, but the guidance is sufficient for a simple tool.
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.
Although many tools are individually well-described, there are several overlapping clusters: three ask_pipeworx variants, multiple polymarket edge/arbitrage tools, and AI-visibility checks vs their competitor-comparison wrapper. An agent can easily pick the wrong one because the boundaries (beta vs stable, grounded vs routed, edge vs arbitrage) are subtle despite the verbose descriptions.
The set is consistently snake_case and mostly readable, so naming is not chaotic. However, the pattern is mixed: some tools use entur_/polymarket_/pipeworx_ prefixes, others are bare verbs (remember, recall, forget), and some are noun phrases (entity_profile, pipeworx_trending). The ask_pipeworx family also doesn't follow the pipeworx_ prefix convention used by neighboring tools.
34 tools is well past the healthy range for a focused MCP server, and only three tools relate to the Entur transport domain implied by the server name. The other 31 tools form a separate, broad data/prediction-market product that appears bolted on, making the count inappropriate for the apparent purpose.
The Entur transport subset has stops search, departures, and journey planning, but misses common public-transport needs such as disruptions, service alerts, and fare/ticket information. The broader tool set is extensive but lacks a single coherent domain to be complete against, leaving the overall surface scattered and hard to trust as an integrated whole.