satoshidata — Bitcoin entity intelligence

network_intelligence

Return the combined Bitcoin network summary for agents: price, fees, mempool, blocks, and satoshidata.ai chain-intelligence context. Set include_charts=true only when chart arrays are needed.

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

Input Schema

Name	Required	Description	Default
`include_charts`	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

A4.1/5.0

Behavior3/5

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

With no annotations, the description must carry the transparency burden. It discloses that charts are conditional and that the output is a summary, but it does not mention potential performance/latency implications of a combined call, data freshness, or any side effects. It is not misleading, but it 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 two sentences: the first states the core purpose, and the second gives precise parameter instruction. There is no redundant or filler content; every word adds value.

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?

Given the tool's simplicity (one optional parameter, output schema present), the description covers the functional scope adequately. It might benefit from noting that it aggregates multiple data sources and could be heavier than individual sibling calls, but this is not essential.

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

Parameters5/5

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

The schema provides only the parameter name and type, but the description adds critical semantic guidance: 'Set include_charts=true only when chart arrays are needed.' This clarifies the parameter's purpose and appropriate usage, exceeding schema coverage.

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

Purpose5/5

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

The description clearly states the tool's function: returning a combined Bitcoin network summary with specified components (price, fees, mempool, blocks, chain-intelligence). The verb 'Return' and the list of content make the purpose specific and distinct from individual market/fee/mempool tools.

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?

The description implies usage when a combined summary is needed, but it does not explicitly contrast with sibling tools like bitcoin_price or mempool_stats. It offers parameter-level guidance for include_charts but lacks direct 'when to use this vs. alternatives' instructions.

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?