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 idempotentHint=true, so the description adds no extra behavioral context. It does not describe side effects like what happens if key is missing, but given annotation coverage, score is adequate.
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, front-loaded with the action and resource, followed by usage guidance. No superfluous words.
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 tool with one parameter, annotations, and no output schema, the description fully covers purpose, usage, and sibling relationships. No 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%, so baseline is 3. The description does not add any additional meaning to the 'key' parameter beyond the schema's description, which is sufficient.
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 a specific verb 'Delete' and resource 'previously stored memory by key', clearly distinguishing the tool's function. It also references sibling tools 'remember' and 'recall', showing its place in a family.
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 the tool: 'context is stale, task is done, or want to clear sensitive data'. It also mentions pairing with 'remember and recall', guiding context on 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.
The tool set includes multiple similar tools (e.g., three ask_pipeworx variants, several Polymarket tools) that could cause agent confusion. While each has a distinct purpose, the boundaries are subtle and descriptions lean heavily on jargon, making misselection likely.
All tool names use snake_case consistently. Most follow a noun_verb or verb_noun pattern, but some (e.g., ai_visibility_check, bet_research) start with a subject rather than an action, breaking a strict verb-first convention.
With 40 tools, the server feels overloaded. The name 'Quotes' suggests a narrow focus, yet the tool set spans fact-checking, company research, prediction markets, and more. Many tools are highly specialized or meta-tools, inflating the count without clear necessity.
The server covers a wide range of use cases, from quotes and literature to financial data and prediction markets. However, there are noticeable gaps in core areas (e.g., basic CRUD for quotes beyond search and random), and the sheer breadth creates dead ends for deep workflows.