satoshidata — Bitcoin entity intelligence

address_risk

Return factual address risk signals: entity label/category, source count, bounded behavioral flags, coarse risk_indicator, and an informational-only disclaimer. This is not AML/KYT/compliance advice.

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_risk"
  }
}

Input Schema

Name	Required	Description	Default
`address`	Yes

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

Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It does disclose the informational nature, bounded flags, coarse risk indicator, and non-advice caveat. However, it does not explicitly state whether the operation is read-only, mention data freshness, or address any side effects, leaving some gaps.

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, front-loaded with the core purpose and output components, and ends with an essential disclaimer. Every sentence contributes value with no unnecessary information.

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?

An output schema exists, so return values are likely detailed there. The description adds context about output categories and limitations. However, it lacks usage guidance and parameter specifics, making it only partially complete for a tool with one parameter and no annotation support.

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?

The only parameter, 'address', has no description in the schema (0% coverage) and the tool description adds no additional meaning beyond the parameter name. It does not specify accepted address formats, networks, or examples, so the agent gains no extra semantic information from the description.

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 returns factual address risk signals and lists specific output components (entity label/category, source count, bounded behavioral flags, coarse risk_indicator, disclaimer). This distinguishes it from siblings like risk_check by emphasizing 'coarse' and 'factual' outputs.

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 a legal disclaimer ('not AML/KYT/compliance advice') but gives no explicit guidance on when to use this tool versus alternatives like risk_check or address_intelligence. There is no mention of appropriate use cases or exclusions beyond the disclaimer.

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?