Skip to main content
Glama

Perp market overview

perp_market_overview
Read-only

One asset's perpetual futures across OKX, Hyperliquid, dYdX and Kraken Futures: mark and index/oracle price, basis (mark vs index, in bps), 24h volume and open interest in USD, and funding — each venue's current or predicted rate with its funding interval, its 8-hour equivalent and simple annualized percentage. Summary: total open interest and volume, highest/lowest and open-interest-weighted 8h funding, and mark-price dispersion across venues. Accepts BTC, BTCUSDT, BTC/USDT or XBT. Venues that fail are listed under errors; the call fails (and is not charged) only if none answers. Costs $0.005 USDC per call.

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

Input Schema

NameRequiredDescriptionDefault
symbolYesBase asset or pair, e.g. 'BTC', 'ETH', 'SOLUSDT'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description goes well beyond them by disclosing partial-failure semantics (failed venues appear under errors), that the call only fails and is not charged when no venue answers, and the exact cost of $0.005 USDC per call. These are precisely the operational facts an agent needs before invoking a paid, multi-source aggregation.

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 first clause front-loads the resource and venue scope, then the payload, then the summary, then operational caveats and price. It is dense but nearly every clause carries information; the funding-rate breakdown is slightly list-like and could be tightened, but nothing is filler.

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?

With no output schema, the description must describe return values itself, and it does: per-venue fields, funding interval/8h/annualized conversions, aggregated summary metrics (weighted funding, dispersion), error behavior, and cost. An agent can predict the response shape and failure modes without further documentation.

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?

Schema coverage is 100% for the single symbol parameter, so the baseline would be 3; the description earns extra credit by explicitly listing accepted input forms (BTC, BTCUSDT, BTC/USDT, XBT), which tells the agent that multiple symbol formats are normalized rather than requiring an exact pair string.

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?

States a specific resource (one asset's perpetual futures across OKX, Hyperliquid, dYdX, Kraken Futures) and enumerates exactly what is returned: mark/index price, basis in bps, 24h volume, open interest, funding with interval, 8h equivalent, annualized rate, plus a cross-venue summary. This is clearly distinguishable from siblings such as funding_rate_arbitrage, open_interest_change, and pair_data without opening any schema.

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 scope of the tool is clear, so the usage context is implied: call it when you need a multi-venue perp snapshot for one asset. However, no sibling is named as an alternative and no explicit when-not guidance is given (e.g., for single-venue funding arbitrage use funding_rate_arbitrage, or for OI deltas use open_interest_change).

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