Skip to main content
Glama
Futuur MCP

Futuur MCP

Official
by futuur

Get order book

get_order_book
Read-only

Retrieve a market’s bid and ask price levels, cumulative totals, last trade, and 24-hour volume to assess liquidity and slippage before placing an order.

Instructions

Returns the order book of one market: resting bid levels (best price first, highest) and ask levels (best price first, lowest), each with the price (0 to 1), shares and amount at that level and the cumulative totals from the best price, plus the last trade price/time and 24-hour volume and trade count. Takes a MARKET id (an item of an event's markets), not an event id. Use it to judge liquidity and slippage before placing an order; only the best levels levels per side are returned, with *_levels_total giving the full depth.

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": {
      "id": "<id>"
    },
    "name": "get_order_book"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMarket id, from the `markets` of get_markets or get_market_details.
levelsNoHow many price levels to return per side, 1 to 100. Default 10.
positionNoWhich side of the market to view: "long" (default) or "short". Short prices are 1 minus long prices.long
currency_modeNo"play_money" (default, OOM) or "real_money" (USDC/USDT) book.play_money

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A4.6/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 by disclosing that only the best `levels` levels per side are returned and that `*_levels_total` carries the full depth — a critical truncation caveat. It also documents the ordering conventions (best price first, highest bid / lowest ask) and the cumulative-total semantics, which materially affect interpretation.

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?

Front-loaded with the core purpose, then the return shape, then the id caveat, then the usage hint. It is dense — the first sentence is a long chain of clauses — but nearly every clause carries information an agent needs, with no filler or repetition.

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?

There is no output schema, so the description bears the full burden of describing return values, and it does so completely: level fields, cumulative totals, last trade price/time, 24h volume and trade count. Combined with the truncation caveat and the id-type warning, an agent has everything needed to call and interpret this tool.

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%, so the schema already carries the per-parameter definitions and the baseline is 3. The description still adds value by stressing the id must come from an event's `markets` and by explaining the relationship between the `levels` cap and the returned `*_levels_total` depth, though it does not discuss `position` or `currency_mode`.

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?

Opens with a specific verb+resource ('Returns the order book of one market') and immediately enumerates the returned content (bid/ask levels, price, shares, amount, cumulative totals, last trade, 24h volume). It also pre-empts the most likely confusion by stating it takes a MARKET id, not an event id, which separates it from market/event listing siblings.

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?

Gives a concrete use case — 'judge liquidity and slippage before placing an order' — which situates it relative to order-placement siblings. It stops short of naming an explicit alternative or a when-not-to-use condition, so it is clear context rather than full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.