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 mark destructiveHint=true, and description adds context about clearing sensitive data. No contradiction, but description adds value 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?
Two sentences: first states purpose, second gives usage guidelines. No wasted words, front-loaded.
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 tool with one parameter and good annotations, the description is complete and sufficient.
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?
Only one parameter 'key' with schema description 'Memory key to delete'. Schema coverage is 100%, so description adds little beyond 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 clearly states the verb (delete) and resource (memory), and distinguishes from sibling tools 'remember' and 'recall' by pairing 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?
Explicitly states when to use: when context is stale, task is done, or to clear sensitive data. Also notes pairing with remember and recall.
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.
Tools have distinct purposes with clear descriptions, but ask_pipeworx_beta currently duplicates ask_pipeworx, and the multiple prediction market tools could be confusing without careful reading.
All tool names follow a consistent snake_case verb_noun or noun_verb pattern, with no mixing of conventions.
34 tools is high for a single server, covering chain data, Pipeworx research, and prediction markets. While well-organized, the breadth pushes the boundary of manageable scope.
The tool set covers major query operations for chains, entities, and data sources, with subscription and memory features. Minor gaps like lack of chain creation are acceptable given the server's focus on data retrieval.