Skip to main content
Glama

Futures data

futures
Read-only

USDT perpetual of the pair on Binance: funding rate and next funding time, mark price, open interest (last 24 h, hourly) and liquidations of the last 24 h summarised: longs and shorts liquidated in USD, the price zones with most liquidations and the 10 largest.

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": {
      "pair": "<pair>"
    },
    "name": "futures"
  }
}

Input Schema

NameRequiredDescriptionDefault
pairYesCoin traded against USDT: BTC, ETH, SOL, XRP, BNB, DOGE, ZEC or NEAR

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The readOnlyHint and openWorldHint annotations already establish the safety profile, and the description adds useful behavioral scope: Binance USDT perpetuals, 24-hour windows, hourly open interest, and a specific liquidation summary composition. It stops short of operational details such as data freshness, rate limits, or response shape, but is substantially more informative than the annotations alone.

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 definition is a single dense sentence with no filler, and each clause enumerates a distinct returned metric or time window. The important scope, USDT perpetual on Binance, is front-loaded before the detailed data list.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read-only data tool with no output schema, the description is complete enough to call correctly: it identifies the pair universe, data source, exact metrics, and time windows. It does not need to explain return values further because the enumerated metrics effectively serve that role.

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 description coverage is 100% and the single pair parameter is fully documented with its enum. The description reinforces that the pair is traded against USDT on Binance but does not add syntax, filtering, or other meaning beyond what the schema already provides, so the baseline score of 3 applies.

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 a specific resource, USDT perpetuals on Binance, and enumerates the exact data returned: funding rate, next funding time, mark price, open interest, and liquidation summaries. This clearly distinguishes it from sibling tools such as candles, big_trades, cvd, market_snapshot, and order_book_walls.

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?

Usage is implied by the data listed: an agent can infer this tool is for futures-specific metrics like funding and liquidations. However, there is no explicit when-to-use guidance, no alternatives named, and no exclusions for when another sibling such as market_snapshot would be preferable.

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