satoshidata — Bitcoin entity intelligence

pulse_whales

Return recent large Bitcoin movements from satoshidata.ai's live on-chain Pulse feed.

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": "pulse_whales"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`since`	No
`min_btc`	No

Output Schema

Name	Required	Description	Default
`ok`	Yes
`data`	No
`error`	No
`endpoint`	Yes
`status_code`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 26, 2026

TDQS

B3/5.0

Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It indicates a read-only operation via 'Return' and adds the 'live on-chain' context, but it does not mention pagination, rate limits, or whether the feed includes unconfirmed transactions, so behavioral disclosure is minimal.

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

Conciseness5/5

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

The description is a single, front-loaded sentence that states the core function without any extraneous wording. It earns its place by conveying the tool's primary purpose efficiently.

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

Completeness2/5

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

Given the extensive list of sibling tools, the description is too sparse to provide sufficient context for correct tool selection. It does not explain how pulse_whales differs from whale_alerts or pulse_dormant, and it omits any usage conditions, making the tool harder to use correctly in a complex environment.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for the three parameters. It hints at 'recent' (since) and 'large' (min_btc) but does not explain limit, the format of 'since', or units for 'min_btc', leaving the agent with incomplete parameter semantics.

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 uses the verb 'Return' with the resource 'recent large Bitcoin movements' and mentions the specific source 'satoshidata.ai's live on-chain Pulse feed', clearly indicating what the tool does. However, it does not compare itself to highly similar siblings like whale_alerts or pulse_dormant, so it loses the full sibling-distinguishing score.

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

Usage Guidelines2/5

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

The description provides no explicit guidance on when to choose this tool over the many sibling pulse/whale tools. There is no mention of exclusions, alternative tools, or use-case conditions, leaving the agent to infer applicability from the name alone.

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

All satoshidata — Bitcoin entity 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?