Skip to main content
Glama

21btc.cc Bitcoin Data

Spot Bitcoin ETF flows

get_etf_flows
Read-onlyIdempotent

US spot Bitcoin ETFs: BTC held, fee, latest/5d/20d/cumulative flows (USD millions). Same data as GET /api/v1/etf. 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_etf_flows"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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=false, so 'Read-only' in the description adds nothing. It does add units (USD millions) and the fact that this mirrors the REST endpoint /api/v1/etf, but omits freshness/update cadence, which matters greatly for flow data.

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?

One dense, front-loaded fragment that names the resource first, then the output fields, then the endpoint equivalence. 'Read-only' is redundant with the annotations and is the one sentence clause that does not earn its place.

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?

With no output schema, the field enumeration (BTC held, fee, 5d/20d/cumulative flows) carries the return-value burden well, and the REST equivalence gives a path to further docs. Missing refresh cadence and whether per-fund breakdowns are included keeps it short of full completeness.

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?

Zero parameters, so the baseline is 4. The description rightly spends no words on arguments and instead documents what comes back, which is the only semantic content available for a no-arg tool.

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 (US spot Bitcoin ETFs) and enumerates the returned measures: BTC held, fee, and latest/5d/20d/cumulative flows with units. It is immediately distinguishable from topic-based siblings like get_derivatives or get_holders, though it never states a verb explicitly and leans on the name.

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?

Provides no explicit when-to-use, when-not, or alternative routing guidance. Selection is only implied by the topic label, which is probably sufficient given siblings are cleanly disjoint domains, but nothing tells the agent to prefer it over e.g. get_price for a related question.

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