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 idempotentHint=true. The description adds context about clearing 'sensitive data' but does not elaborate on other behavioral aspects like irreversibility or error handling. Given annotations, the description provides moderate added value.
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?
The description is three concise sentences: action, usage conditions, and pairing advice. Every sentence adds value, and the most important information is front-loaded in the first sentence.
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, single-parameter tool with annotations (destructiveHint, idempotentHint) and no output schema, the description covers the essential behavioral and usage context. The pairing recommendation with 'remember' and 'recall' completes the picture.
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 the schema describing 'key' as 'Memory key to delete'. The description echoes this and adds context about the key referencing a 'previously stored memory', but does not significantly extend the schema's meaning.
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 tool's purpose: 'Delete a previously stored memory by key.' It uses a specific verb (Delete) and a well-defined resource (memory by key), and distinguishes it from siblings like '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?
The description provides explicit usage scenarios: 'Use when context is stale, the task is done, or you want to clear sensitive data the agent saved earlier.' It also suggests pairing with 'remember' and 'recall', but does not explicitly state when not to use this tool or contrast with alternative tools beyond the 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.
Most tools have clearly distinct purposes, but there is some overlap among data query tools like ask_pipeworx, ask_pipeworx_grounded, deep_research, entity_profile, compare_entities, and recent_changes. However, detailed descriptions and different use cases help an agent distinguish them, so it is mostly clear.
All tool names follow a consistent lower_snake_case pattern with a verb_noun style (e.g., ask_pipeworx, list_subscriptions, validate_claim). There are no mixed conventions, making it predictable and easy to understand.
With 31 tools, the server covers a broad domain of data queries, prediction markets, memory, and subscriptions. While slightly more than typical, each tool earns its place and the count is reasonable for the comprehensive platform scope.
The tool surface is extensive, covering data querying, analysis, entity resolution, comparison, change tracking, memory, subscriptions, and more. There are no obvious gaps; it supports a wide range of user intents for the server's purpose.