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 indicate destructiveHint=true and idempotentHint=true. The description adds context about clearing sensitive data, which enhances transparency beyond the 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?
Three sentences, no fluff. First sentence states core purpose, second gives usage guidance, third references siblings. Front-loaded and efficient.
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 single-parameter tool with no output schema and good annotations, the description covers purpose, usage, and related tools without gaps.
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%, and the description's 'by key' aligns with the key parameter but does not add additional meaning 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, and distinguishes from sibling tools by mentioning '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?
Explicitly states when to use: 'when context is stale, the task is done, or you want to clear sensitive data'. Also provides sibling references for alternative actions.
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.
Each tool has a clear, distinct purpose. The various `ask_pipeworx*` variants are differentiated by mode (single vs grounded vs research). `get_nav_history` vs `latest_nav` serve different query granularities. Administrative tools like `remember`/`recall`/`forget` are clearly separate. No two tools overlap in functionality.
Tool names follow a consistent snake_case convention and generally use `verb_noun` order (e.g., `ask_pipeworx`, `search_schemes`, `validate_claim`). A few exceptions like `entity_profile` (noun_verb) exist, but the pattern is mostly predictable.
At 34 tools, the server is quite large, including many specialized tools (e.g., multiple Polymarket tools, administrative memory/subscription tools) that could arguably be split into separate servers. The number feels slightly excessive for a coherent, focused server.
The tool set covers an extraordinarily wide range of domains: company financials, SEC filings, FDA drugs, economic data, mutual funds, real estate, prediction markets, npm dependencies, AI visibility, and more. It also includes memory, subscription, and feedback mechanisms. There are no obvious gaps for the domains addressed.