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 provide destructiveHint=true and readOnlyHint=false. The description adds useful behavioral context about why to delete (stale context, sensitive data), enhancing transparency beyond annotations.
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 two sentences with no wasted words. It front-loads the action and purpose, then provides usage guidelines.
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 delete-by-key tool with no output schema, the description covers the action, when to use, and pairing with siblings. It is complete for the level of complexity.
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 parameter description 'Memory key to delete'. The description adds no new semantic information beyond the schema, so baseline 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 uses the strong verb 'Delete' and specifies the resource 'previously stored memory by key'. It also distinguishes from siblings by stating 'Pair with remember and recall.'
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 states when to use the tool: 'when context is stale, the task is done, or you want to clear sensitive data the agent saved earlier.' It also mentions pairing with related tools.
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 tools answer factual questions (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, validate_claim, deep_research), and ask_pipeworx_beta is explicitly identical to the stable router right now, creating genuine selection ambiguity. Most other clusters—memory, subscriptions, entity research, Polymarket—are reasonably distinct once the verbose descriptions are read.
Names are consistently lowercase snake_case with recognizable family prefixes (ask_pipeworx_*, data360_*, polymarket_*, pipeworx_*), which aids grouping. The convention mixes verb-first names like resolve_entity with noun/prefix names like polymarket_edges, but it is still readable and predictable enough.
34 tools is well past the heavy range, and the server bundles several unrelated concerns—universal data routing, prediction-market analytics, memory, subscriptions, AI-visibility marketing, and npm dependency scanning—into one surface. Many tools earn their place, but the aggregate is overloaded and likely to slow tool-selection.
The data-research side has strong coverage: discovery, universal routing, grounded verification, entity resolution, profiles, comparisons, recent-changes tracking, and in-record search. Subscription lifecycle and memory are complete, and the prediction-market suite even covers fill-risk and edge persistence; only a few niche read/write operations are absent.