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 and idempotentHint, and the description adds context about deleting stored memories by key and clearing sensitive data, without contradicting the annotations.
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, no unnecessary 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?
Simple tool with one fully documented parameter, safety annotations, and clear usage intent; description covers what, when, and related tools, making it complete for an agent.
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 description covers 100% of the parameter with 'Memory key to delete', so the description's mention of 'by key' adds no extra semantics beyond the schema.
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?
Explicitly states the verb 'Delete' and the resource 'previously stored memory by key', clearly distinguishing it from sibling tools like remember and recall which perform other memory operations.
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 usage guidance: 'Use when context is stale, the task is done, or you want to clear sensitive data...' and mentions pairing with remember and recall, giving clear context for when to invoke.
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 major clusters are distinct (blockchain explorer, memory, subscriptions), but several tools have unclear boundaries: ask_pipeworx_beta is currently identical to ask_pipeworx, the three ask_pipeworx variants and deep_research all route questions, and the five Polymarket tools overlap heavily on edge detection. An agent would struggle to pick the right query tool or prediction-market tool without reading very long descriptions.
Naming is a mix of single-word nouns (address, block, node, transaction, stats), verb-noun snake_case (validate_claim, generate_llms_txt), and noun-phrase snake_case (entity_profile, bet_research), with no consistent style or verb convention. There is no predictable pattern an agent can generalize from.
36 tools is well above the comfortable range, and most are meta-tools for Pipeworx, Polymarket, memory, and subscriptions rather than Blockchair blockchain functionality. A large share of the count is redundant query and edge-analysis variants, so the size adds confusion rather than capability.
As a read-only research and monitoring gateway, the surface is fairly complete: universal routing, grounded answers, entity resolution, profiles, comparisons, claim validation, memory, and subscriptions all have lifecycle coverage. Relative to the Blockchair name, the blockchain side is thin but covers address, block, transaction, node, and stats, with only minor gaps like mempool or raw script details that agents can work around.