Skip to main content
Glama

Crypto Derivatives Data API

Crypto derivatives snapshot (one coin, one call)

derivatives_snapshot
Read-only

Crypto derivatives snapshot of one coin in one call: perp funding rates per exchange with predicted funding, open interest (OI) per venue, perp premium and the nearest futures basis, 24h liquidations and the long/short ratio. Venues: Bybit, Hyperliquid, dYdX, Gate, Kraken, Bitfinex, Deribit, OKX. The derivatives data bundle for trading agents on BTC, ETH, SOL and more. Data only. Bad input is free; under 3 venues not charged. Price: $0.005 per successful call, paid over x402 (USDC on Base); pass the payment in _meta["x402/payment"].

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": {
      "coin": "<coin>"
    },
    "name": "derivatives_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinYesCoin symbol: BTC, ETH, SOL, PEPE ... (also BTCUSDT, BTC-PERP, XBT, 1000PEPE, kPEPE).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  3. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Annotations already establish read-only and open-world behavior, and the description adds substantial context on top: a concrete price ($0.005 per successful call), the payment rail (x402, USDC on Base, passed via _meta["x402/payment"]), and the billing edge cases (bad input free, fewer than 3 venues not charged). That is exactly the cost/auth information an agent cannot get from annotations or schema.

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: what it returns, then venues, then pricing and payment. Most sentences carry load, but 'The derivatives data bundle for trading agents on BTC, ETH, SOL and more' is promotional filler that duplicates the opening clause and could be cut without loss.

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 describing returns and it does enumerate the metric families and venues, which is enough for an agent to judge relevance. It stops short of describing the response structure or what happens when fewer than three venues have data (beyond 'not charged'), a minor gap for a multi-venue aggregation tool.

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

Parameters3/5

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

Schema coverage is 100% and the single coin parameter is already documented with accepted symbol variants (BTCUSDT, XBT, 1000PEPE). The description adds only the scoping constraint that it is one coin per call; the venue list is about output, not the input. Baseline 3 is appropriate when the schema does the work.

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?

The description names a specific resource and scope: a single-coin derivatives snapshot combining funding rates, OI, premium/basis, liquidations and long/short ratio, across eight named venues. It distinguishes itself from siblings implicitly via 'one coin in one call' and 'bundle', making clear it aggregates what perp_funding_rates, open_interest, futures_basis and liquidations return separately, though it never names those siblings outright.

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 phrase 'one call' and 'the derivatives data bundle for trading agents' implies you should use this when you need several derivatives metrics at once rather than one. However, there is no explicit when-to-use vs. when-not guidance and no sibling tool is named as an alternative, so the agent must infer that the single-metric tools are the fallback.

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.