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 destructiveHint=true and idempotentHint=true, and the description states 'Delete' which is consistent. No additional behavioral details (e.g., if deletion fails silently, or cascading effects) are disclosed, but the annotation coverage is sufficient.
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 achieve high density of information: first states the core action, second provides usage guidance. No filler or redundant content.
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, clear annotations, and no output schema, the description adequately covers purpose, usage, and parameter meaning. No missing context.
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 single parameter 'key' described as 'Memory key to delete'. The description does not add any further details about the parameter, so it meets the baseline expectation but provides no extra value.
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 action ('Delete'), the resource ('previously stored memory'), and the mechanism ('by key'). It distinguishes itself from sibling tools 'remember' and 'recall' by focusing on deletion.
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 scenarios for use: stale context, task completion, clearing sensitive data. Mentions pairing with remember and recall. Lacks explicit when-not-to-use or alternative tools for similar operations.
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.
Most tools have distinct purposes, but there is notable overlap among ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research—all of which route questions to the same underlying catalog. The polymarket_* family also has several opportunity-scanning tools (edges, arbitrage, bet_research) that agents could confuse without reading the long descriptions carefully.
All 34 tool names use lowercase snake_case with a clear verb-first or noun-descriptive pattern (list_feeds, read_feed, remember, resolve_entity, polymarket_arbitrage). Even compound names like ai_visibility_check and ask_pipeworx_grounded follow a predictable, consistent style. No mixed conventions or camelCase deviations.
34 tools is far more than the apparent 'Gaming Feeds' scope suggests—only list_feeds, read_feed, and fetch_feed actually relate to gaming feeds. The rest form a sprawling data-research and prediction-market suite, creating a severe mismatch between the server name and its actual tool surface.
Viewed as a general Pipeworx data-access platform, the tool set is quite complete: question routing, grounded answers, entity resolution, profiles, comparisons, claim validation, memory, subscriptions, alerts, feed reading, and tool discovery are all covered. The only notable gaps are feed management (no create/update/delete for custom feeds) and a few odd add-ons like generate_llms_txt that feel outside the core domain.