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 readOnlyHint=false, so the description's 'Delete' verb is consistent. The description adds context about clearing sensitive data, but no additional behavioral traits beyond what annotations provide. No contradiction.
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 with no wasted words: first sentence states the action, second provides usage context, third mentions related tools. Efficient and 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 tool with one parameter, the description covers purpose, usage, and relationships. No output schema needed. Complete enough for an agent to select and invoke correctly.
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 one parameter 'key' described as 'Memory key to delete'. The description ('by key') adds no new meaning beyond the schema. Baseline 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?
The description uses a specific verb ('Delete') and resource ('previously stored memory by key'), clearly stating the tool's function. It also distinguishes itself from sibling tools like 'remember' and 'recall' in the last sentence.
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'. Mentions pairing with 'remember' and 'recall'. Lacks explicit when-not cases, but still offers clear guidance.
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 are richly described with clear use-cases, but several clusters overlap: ask_pipeworx/ask_pipeworx_beta/ask_pipeworx_grounded/deep_research are all question-routing tools with similar names, and the five polymarket_* tools cover adjacent prediction-market analysis. An agent could easily pick the wrong one without reading the full descriptions.
All names are snake_case and mostly follow a verb_noun or domain_noun pattern (compare_entities, resolve_entity, denver_query, polymarket_edges, pipeworx_trending). There are minor deviations like single verbs (remember, forget), adjective-first names (recent_alerts, deep_research), and domain-prefixed groups, but the overall style is predictable and readable.
34 tools is a large surface for one server, pushing beyond the 25+ threshold where agents struggle to choose. While the platform is genuinely multi-domain (data lookup, prediction markets, Denver open data, memory, subscriptions, npm checks, llms.txt generation), several niche clusters like the 5-tool Polymarket suite and 3-tool memory trio inflate the count.
The server covers its domain well: general querying, grounded verification, deep research, entity resolution, company profiling, change feeds, subscription lifecycle (subscribe/list/unsubscribe/alerts), memory lifecycle (remember/recall/forget), and discovery (discover_tools, suggest_questions). Minor gaps exist—such as no direct browsing of all Pipeworx sources—but agents can work around them.