satoshidata — Bitcoin entity intelligence

risk_check

Return a free evidence + confidence BTC screening bundle for one address, not a recommendation; you decide whether to transact.

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

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

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool is free and returns evidence + confidence but not a recommendation, yet it omits other behavioral aspects like data sources, update frequency, limitations, or whether any side effects occur. The phrase 'you decide whether to transact' adds interpretive context, but the 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 entire description is a single, dense sentence that packs purpose, cost, scope, and a disclaimer without unnecessary words. It is front-loaded with the main action and reads efficiently.

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?

The tool is simple (one parameter) and has an output schema, so return values are covered elsewhere. However, with no annotations and no mention of sibling tools or ecosystem positioning, the description leaves the agent to infer where this fits relative to address_risk, risk_check_batch, and other screening tools.

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 coverage is 0% and the description only mentions 'one address' without adding format, validation, or example. The parameter 'address' is self-explanatory from its name, but the description does not compensate for the lack of documented details beyond what the schema already provides.

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 what the tool does with a specific verb ('return') and identifies the resource: a free evidence + confidence BTC screening bundle for a single address. It also explicitly distinguishes itself as 'not a recommendation' and implicitly separates from batch tools like risk_check_batch.

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 a use case (quick free screening of one address before a transaction) and includes the caveat that it is not a recommendation. However, it offers no explicit when-to-use versus alternatives or exclusions, such as pointing to risk_check_batch for multiple addresses.

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?