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 declare destructive and idempotent behavior. Description adds 'sensitive data' context but lacks details on edge cases like key not found or return value. Acceptable but not exceptional.
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, front-loaded with purpose, no redundancy. Every sentence adds value.
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?
Complete for a single-parameter destructive tool with good annotations. Includes purpose, usage guidelines, and pairing advice. No output schema needed.
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 covers 100% of parameters with description 'Memory key to delete'. Description adds no new meaning beyond 'by key', so 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?
Clearly states the tool deletes a memory by key, using specific verb 'delete' and resource 'memory'. Distinguishes from siblings 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?
Provides explicit when-to-use scenarios: stale context, task completion, clearing sensitive data. Names alternatives (remember, recall) and suggests pairing.
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 have overlapping purposes, such as ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, and specialized tools like entity_profile or validate_claim that can answer similar questions. This creates ambiguity for an agent trying to select the correct tool.
All tool names follow a consistent snake_case pattern, with most using a verb_noun structure (e.g., ask_pipeworx, compare_entities, resolve_entity). There are no mixed conventions or chaotic naming.
With 31 tools, the server is on the heavy side. While each tool has a distinct purpose, the number is borderline for a coherent set and could be streamlined, especially given the overlapping functionality.
The tool set covers a wide range of query and analysis tasks, including data lookup, comparison, betting research, memory, and subscriptions. However, there are notable gaps (e.g., no update/delete for most data, no user management) and some tools seem out of place (e.g., generate_llms_txt).