Diamond Bitcoin Intelligence

Whale flow statistics, last 24 hours

bitcoin_whale_stats_24h

Read-onlyIdempotent

Whale flow statistics for the last 24 hours from this node: count and US$ volume of transactions of US$100,000 or more per hour, size bands, mempool vs block split and the 10 largest transactions. Paid per call. Price: 10 sats or US$0.01 (USDC) per call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bitcoin_whale_stats_24h"
  }
}

Input Schema

Name	Required	Description	Default
`l402`	No	Optional. After paying the Lightning invoice: '<token>:<preimage>'.
`pay_with`	No	Optional. 'lightning' returns a BOLT11 invoice and a token instead of the x402 payment request.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A3.7/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false. The description adds valuable context beyond annotations: it states the tool is paid per call and gives the price (10 sats or US$0.01 USDC), and clarifies the data is from 'this node'. It does not explain payment failure behavior or rate limits, but the pricing disclosure is a key behavioral trait.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences: the first packs purpose and data details, the second covers payment. It is front-loaded with the core purpose and has no unnecessary wording, though the first sentence is dense. It earns its place by conveying both content and cost efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and two optional parameters, the description provides a good overview of what is returned (count, volume, size bands, mempool/block split, top 10 transactions) and the payment requirement. It does not specify exact output structure, but the summary is sufficient for an agent to understand the tool's value. Slight gap in not explaining the l402 payment flow, but the schema covers that.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with both optional parameters (l402 and pay_with) fully documented in the schema. The description adds no additional meaning about these parameters, so the baseline of 3 is appropriate since the schema carries the full burden.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description specifies the resource (whale flow statistics) and exact scope (last 24 hours, from this node) along with the data dimensions: count, US$ volume, size bands, mempool vs block split, and top 10 transactions. It does not explicitly differentiate from sibling tools like bitcoin_whales_live, but the 24-hour window is a clear distinguishing factor.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the scope: an agent seeking 24-hour whale flow data would select this tool. However, there is no explicit when-to-use vs alternatives guidance, no mention of prerequisites, and no exclusions. The phrase 'from this node' hints at a data source limitation but is not elaborated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Diamond Bitcoin Intelligence tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?