Skip to main content
Glama

Full briefing for one pair

pair_briefing
Read-only

Everything the radar knows about one perpetual pair in a single answer: funding rate and receiving side, time to next settlement, mark price, 24h volume, open interest with deviation from the 7-day norm, orderbook walls with break-through history, how the price usually moves around settlement, and the same coin on other exchanges. Accepts an exact symbol (BTCUSDT) or just the coin (BTC).

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": {
      "exchange": "<exchange>",
      "symbol": "<symbol>"
    },
    "name": "pair_briefing"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the summary and links: 'en' (default) or 'ru'
symbolYesNative pair symbol (BTCUSDT, BTC-USDT-SWAP) or base coin (BTC)
exchangeYesExchange id

Output Schema

NameRequiredDescriptionDefault
dataYesCompact numbers the conclusion is based on, units named inside
linkYesLive page with the same data
summaryYesOne-line conclusion — quote this

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / exchange / enum
      Previous value: -[
      -  "binance",
      -  "bybit",
      -  "okx",
      -  "bitget",
      -  "hyperliquid"
      -]New value: +[
      +  "binance",
      +  "bybit",
      +  "okx",
      +  "bitget",
      +  "hyperliquid",
      +  "gate",
      +  "aster",
      +  "bitunix"
      +]
  2. First observed

TDQS

A3.7/5.0
Behavior3/5

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

readOnlyHint already establishes the safety profile, and the description stays consistent with it. It adds substantive content context (that orderbook walls come with break-through history, that OI is shown against a 7-day norm, that price behavior around settlement is included), which goes beyond the annotation. It says nothing about data freshness, rate limits, or that part of the payload is a language-dependent narrative summary, so behavioral coverage is partial rather than rich.

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 purpose is front-loaded before the contents enumeration, and the second sentence usefully isolates the symbol flexibility. The middle list is long but each item names a distinct data domain, so little is filler. Slight trim possible, but structure is sound.

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 an output schema present and full parameter documentation, the description only needs to frame scope and content, which it does thoroughly. The notable omission is that lang governs a generated summary and links, which the description never signals, leaving an agent unaware that output text varies by language choice.

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%, so all three parameters are already documented, including the exact-symbol-or-base-coin flexibility and the lang enum. The description's closing sentence restates the symbol flexibility already present in the schema, and it never mentions lang even though that parameter changes the summary and links. Baseline 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 opens with a specific verb and resource ('Everything the radar knows about one perpetual pair in a single answer') and then enumerates the concrete data domains covered: funding rate and side, settlement countdown, mark price, volume, OI deviation, orderbook walls, settlement-adjacent price behavior, cross-exchange comparison. This scope statement clearly separates it from a search tool or a single-metric history tool.

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 only implied: 'in a single answer' suggests reaching for this when a full picture of one pair is needed rather than a targeted metric. There is no explicit when-not-to-use, no pointer to siblings like funding_history or spread_pairs for narrower questions, and no cost/latency framing to help an agent choose between the broad briefing and a cheap single-metric call.

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