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 and idempotentHint, and the description's 'Delete' aligns with these. The description adds context about clearing sensitive data and that the memory was previously stored, which goes beyond annotations without contradicting them.
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 three sentences, front-loaded with the core purpose, and contains no redundant wording. Each sentence adds useful context, making it appropriately sized for the tool's simplicity.
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, the description covers purpose, usage scenarios, parameter semantics, and sibling relationships. The annotations provide safety profile, making the description complete without needing more detail.
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% for the 'key' parameter, but the description adds meaning by stating it deletes a 'previously stored memory by key', implying the key is one created by remember. This adds semantic value beyond the schema's minimal description.
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 deletes a previously stored memory by key, using a specific verb and resource. It distinguishes itself from sibling tools like remember and recall by explicitly pairing with them.
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 scenarios: 'when context is stale, the task is done, or you want to clear sensitive data.' It also mentions pairing with remember and recall, clarifying its role against 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 have significantly overlapping purposes, especially the ask_pipeworx family, deep_research, and validate_claim, plus a dense cluster of polymarket_* tools and two AI-visibility checkers. The ship-related tools are distinct, but an agent would struggle to choose among the many broadly similar query/research tools.
Names are mostly snake_case and readable, but they follow no consistent convention: generic one-word verbs like remember and forget sit alongside branded names like ask_pipeworx, noun-style names like entity_profile, and prefix families like polymarket_*. The inconsistency is noticeable but not chaotic.
34 tools is well above the well-scoped range, and the vast majority are unrelated to the server name 'Vessel Tracking'. The live-ship tools are a tiny minority buried inside a broad general-purpose data, research, and prediction-market platform, making the overall set feel bloated and misaligned with its stated identity.
As a vessel-tracking server, the surface is severely incomplete: only ais_coverage_check, live_ship_position, and live_ships_in_area relate to shipping, with no vessel lookup by name/IMO, no historical positions, no voyage data, and no port-call information. The actual tool set is rich as a general data platform, but that is not what the server name promises.