Return mining-pool attribution by block height/hash, known pool name, or candidate payout address. Block identifiers use /v1/blocks, pool names use /v1/pools/{pool_name}, and addresses use wallet trust-safety.
| Name | Required | Description | Default |
|---|---|---|---|
| address | No | ||
| pool_name | No | ||
| block_hash | No | ||
| block_height | No |
| 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?
No annotations provided, so description carries full burden. Only implies read operation via 'Return' but does not explicitly confirm idempotency, rate limits, or side effects. Lacks disclosure on multiple parameter handling.
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 concise sentences, front-loaded with purpose, no redundancy. Every word adds value.
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?
Output schema exists, reducing need to describe returns. Description covers core functionality and identifier types. Lacks detail on multiple parameter behavior and error handling, but adequate given tool simplicity.
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?
With 0% schema coverage, description adds meaning by mapping 'block height/hash' to params and noting endpoint patterns. However, does not explain parameter precedence or provide complete semantics for each param.
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?
Clearly states verb 'Return', resource 'mining-pool attribution', and specifies three distinct identifiers (block height/hash, pool name, address). Differentiates from sibling tools like pool_detail/pool_list by focusing on attribution lookup.
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?
Mentions API endpoint patterns per parameter but provides no explicit guidance on when to use this tool versus alternatives, no exclusions, and no context on parameter precedence or conflicts.
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.