Skip to main content
Glama

21btc.cc Bitcoin Data

Bitcoin holders: companies, funds, governments

get_holders
Read-onlyIdempotent

Bitcoin holders: companies, funds, governments (BTC, 7-day change). Same data as GET /api/v1/holders. Read-only.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint, so the safety profile is fully covered and 'Read-only' merely restates it. The description does add some value by identifying the upstream endpoint (GET /api/v1/holders) and the data shape (BTC amounts plus 7-day change), but says nothing about freshness, coverage, or response size.

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

Conciseness4/5

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

Extremely short and front-loaded: the resource and its contents come first, then the endpoint mapping. It is telegraphic to the point that the reader must infer whether the response is a list or a snapshot, and 'Read-only' duplicates the annotations, but there is no wasted bulk.

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?

With no output schema, no parameters, and no examples, the description is the only place an agent can learn what the response looks like, and it only gestures at it ('BTC, 7-day change'). For a simple no-arg read endpoint that is barely adequate, and the missing sibling differentiation leaves a real gap.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies; the description cannot add or detract meaningfully here.

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?

Names the specific resource (Bitcoin holders broken into companies, funds, governments) and the metric context (BTC, 7-day change), so an agent knows what data comes back. It does not, however, distinguish itself from the sibling get_holder_distribution, which an agent could easily confuse with this one.

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?

There is no statement of when to use this tool versus alternatives, and no mention of the closely related get_holder_distribution or get_etf_flows. The only routing hint is the API endpoint mapping, which is not usage guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources