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?
The description states 'Delete', which matches the destructiveHint annotation. The idempotentHint is implied but not elaborated. The description adds minimal behavioral context beyond what annotations already provide.
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 extremely concise with two sentences and a pairing hint. Every sentence adds value without unnecessary verbosity.
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?
Given the simple tool (one param, no output schema), the description completely covers purpose, usage, and context. Nothing essential 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?
With 100% schema coverage, the description adds little beyond 'by key'. The schema already describes 'Memory key to delete'. The baseline of 3 is appropriate.
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 'Delete a previously stored memory by key', which is a specific verb and resource. However, it does not explicitly differentiate from sibling tools like 'remember' and 'recall', though it suggests 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 use cases: 'when context is stale, the task is done, or you want to clear sensitive data.' It also suggests pairing with sibling tools. It lacks explicit when-not-to-use or alternative tool 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.
Multiple tool clusters blur together: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, validate_claim, and bet_research all route natural-language questions to sources with overlapping response shapes. The Polymarket family is better differentiated, but an agent faces real selection risk among the query family.
All tools use snake_case, which is good, but verb conventions vary widely: ask_/get_/search_/list_/validate_/generate_/scan_ plus noun-only names like ai_visibility_check, entity_profile, bet_research, and the pipeworx_* prefix. The pattern is readable but not predictable enough to guess a tool's function from its name alone.
34 tools is well past the 25+ threshold for a coherent tool set. The server tries to be a universal data gateway, prediction-market toolkit, memory store, subscription manager, WoRMS lookup, and dependency scanner all at once—scope creep that makes the surface unreasonably large.
For a data-access server there are notable holes: pipeworx:// citation URIs are advertised as fetchable but no tool resolves them directly; subscriptions can be created, listed, and cancelled but not updated or paused; and the WoRMS component (which matches the 'Worms' server name) has only three lookup tools with no synonym/distribution/export coverage.