satoshidata — Bitcoin entity intelligence

address_intelligence

Return the premium satoshidata.ai address-intelligence card for a single Bitcoin address, including current best label, live wallet activity, cohort hints, and scanner signals.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "address": "<address>"
    },
    "name": "address_intelligence"
  }
}

Input Schema

Name	Required	Description	Default
`address`	Yes	Bitcoin wallet address to enrich.

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.3/5.0

Behavior2/5

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

With no annotations, the description carries the full burden but only reveals the output composition, not behavioral traits like whether the call is read-only, premium costs, data latency, or error handling. It does not mention any side effects or access constraints, so the agent lacks safety and expectation-setting context.

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 names the action, resource, and key output components efficiently. Every phrase carries meaningful information without fluff, making it easy to parse.

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

Completeness3/5

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

While the tool has an output schema and a simple parameter, the description doesn't address why one would choose this 'premium' card over similar address tools, nor does it mention any operational constraints (rate limits, cost, data freshness). It is adequate for understanding the return shape but not richly contextual for selection among siblings.

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?

The input schema already fully describes the single 'address' parameter with a clear definition ('Bitcoin wallet address to enrich'), covering 100% of the schema. The description adds no additional parameter semantics beyond what the schema provides, so the baseline score of 3 applies.

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 action ('Return') and the specific resource (the premium address-intelligence card) with detailed content types (best label, live wallet activity, cohort hints, scanner signals), distinguishing it from generic address tools. The inclusion of 'single Bitcoin address' clarifies scope.

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 gives no guidance on when to use this tool versus the many sibling tools like address_risk or address_evidence_pack. It does not state exclusions, prerequisites, or preferability conditions, leaving the agent to infer applicability from the output card contents 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?