Skip to main content
Glama

21btc.cc Bitcoin Data

Bitcoin derivatives: open interest, funding, liquidations

get_derivatives
Read-onlyIdempotent

BTC perpetual futures on Binance, Bybit, OKX and Deribit: open interest (BTC and USD), mark price, funding rate per interval and annualised, a 30-day Binance open interest history and recent OKX liquidations. Public keyless exchange APIs, cached 60 seconds. Liquidations cover one exchange only; no free all-exchange total exists. Not advice. 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_derivatives"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: public keyless exchange APIs (no auth needed), a 60-second cache (staleness expectations), and the one-exchange limitation on liquidations. It doesn't mention rate limits or per-venue failure modes, which keeps it at 4.

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?

The content is front-loaded with the resource and venue list, then caveats and provenance. Every clause carries information (fields, exchanges, cache, coverage limit, disclaimer), though the disclaimer and 'Read-only' tail are partially redundant with annotations. It's dense but not padded.

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 description carries the burden of explaining return contents, and it does so by enumerating the metrics and their units (BTC/USD, interval vs annualised). Coverage limitations and caching are disclosed. What's missing is any sense of output shape or ordering, but for a zero-parameter bundle tool this is close to complete.

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 to disambiguate and the baseline of 4 applies. The description correctly signals a no-argument call by describing a fixed bundle of metrics rather than any inputs.

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 names the concrete resource (BTC perpetual futures) and enumerates exactly what it returns: open interest in BTC and USD, mark price, funding rate per interval and annualised, 30-day OI history, and OKX liquidations. It also names the four venues covered, which lets an agent distinguish it from siblings like get_price or get_volatility without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description establishes clear context for when this is the right tool (derivatives metrics unavailable from spot price tools) and includes an implicit exclusion: liquidations cover one exchange only and no free all-exchange total exists, which tells the agent not to over-claim coverage. It stops short of explicitly naming an alternative sibling to use in any case, so it falls short of a 5.

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