Return free evidence + confidence BTC screening bundles for up to 100 addresses, not recommendations; you decide whether to transact.
| Name | Required | Description | Default |
|---|---|---|---|
| addresses | Yes | Bitcoin addresses to screen, in result order. |
| Name | Required | Description | Default |
|---|---|---|---|
| ok | Yes | ||
| data | No | ||
| error | No | ||
| endpoint | Yes | ||
| status_code | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden. It mentions the tool returns free evidence and confidence, and that it's not a recommendation. However, it does not disclose idempotency, rate limits, or handling of invalid addresses.
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 a single sentence that front-loads the purpose and key traits. It is concise but could be slightly clearer if broken into two sentences.
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?
Given the existence of an output schema, the description appropriately covers the essential context: what is returned (evidence and confidence bundles), constraints (up to 100 addresses), and interpretation (not recommendations). It is complete for a screening tool.
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% and includes a description for the 'addresses' parameter. The tool description adds no further parameter semantics beyond what the schema already provides.
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 it returns 'free evidence + confidence BTC screening bundles' for up to 100 addresses, and explicitly distinguishes from similar tools by noting 'not recommendations; you decide whether to transact.' This differentiates it from siblings like 'risk_check' and 'batch_risk_signals'.
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 implies use for batch screening multiple addresses (up to 100) and that the result is evidence, not a recommendation. It provides guidance on interpretation but does not explicitly state when to avoid or alternatives.
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 cover similar address intelligence (e.g., address_intelligence, address_risk, risk_check, wallet_summary) and dormant coin detection (pulse_dormant, dormancy_flushes, chain_awakenings), causing potential confusion despite descriptive names. Some overlap exists but descriptions help differentiate.
Tools use snake_case and generally follow a verb_noun or noun_verb pattern (e.g., address_evidence_pack, batch_intelligence, fees_recommended). However, a few tools like submit_feedback and verify_timestamp start with verbs, while others start with resources, causing minor inconsistency.
44 tools is high for a wallet intelligence server, covering many subdomains (address, batch, blockchain, mempool, mining, timestamping, etc.). While each tool has a specific purpose, the count feels heavy and could be consolidated, but it's not extreme given the broad scope.
The tool set thoroughly covers Bitcoin wallet and on-chain intelligence: address lookup, risk, evidence, batches, blocks, mempool, fees, mining pools, timestamping, transaction broadcast/verification, pulse feeds, whales, and more. No obvious gaps for the stated purpose.