Verify a detached OpenTimestamps proof against the Bitcoin blockchain.
| Name | Required | Description | Default |
|---|---|---|---|
| proof_base64 | Yes |
| 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 are provided, so the description must communicate behavioral traits. It only states that it 'verifies', without disclosing side effects (e.g., read-only), error handling, or prerequisites. This is a significant gap for a verification tool.
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?
A single, clear sentence with no redundant words. The description is 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 one-parameter tool with an output schema, the description covers the core purpose but lacks usage guidance and behavioral details. It is minimally adequate but leaves out important context like what happens when a proof is invalid.
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 0%, so the description must compensate. It mentions 'detached OpenTimestamps proof', which gives context to the proof_base64 parameter, but it does not elaborate on format requirements or constraints beyond what the param name implies. Partial compensation only.
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 specific action: verifying a detached OpenTimestamps proof against the Bitcoin blockchain. This distinguishes it from sibling tools like timestamp_hash and timestamp_quote, which involve different steps in the timestamping process.
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 usage when you have a detached OpenTimestamps proof to verify, but it does not explicitly mention when to use this tool versus alternatives like timestamp_hash or tx_verify. It lacks explicit exclusions or alternative tool references.
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.
Several tool clusters have unclear boundaries: address_evidence_pack, address_intelligence, address_risk, risk_check, wallet_detail, wallet_summary, and wallet_trust_safety all return address-related intelligence with subtle differences. Similarly, pulse_dormant, chain_awakenings, and dormancy_flushes all describe dormant-coin reactivation events, and whale_alerts overlaps heavily with pulse_whales. Agents will likely struggle to select the correct tool without deep domain knowledge.
Tool names predominantly follow a snake_case convention with domain-prefix patterns (address_*, batch_*, entity_*, mempool_*, pulse_*, timestamp_*, tx_*, wallet_*). There are minor deviations like op_return_decode (object-verb ordering) and some noun-only names, but overall the pattern is predictable and readable.
With 44 tools, this is a large surface that exceeds the 'too many' threshold in the calibration scale. While the server covers a broad Bitcoin intelligence domain, the sheer number of tools—especially with overlapping functionality—makes it feel bloated and difficult to navigate.
The tool set covers virtually every major aspect of Bitcoin intelligence: address analysis, entity rollups, mempool state, network stats, mining pools, on-chain pulse events, transaction verification, timestamping, and batch operations. There are no obvious dead ends or missing capabilities for the stated purpose.