Skip to main content
Glama

Microverse Market Data

Get order book

get_order_book
Read-onlyIdempotent

Live order book for one symbol on one venue: bids and asks as [price, size], best levels, mid, spread (absolute and basis points), last trade, feed status and book age. symbol can be loose ('BTC', 'BTC-USDT', 'BTCUSDT') or an exact Kalshi/Polymarket ticker. depth is per side (max 50).

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

Input Schema

NameRequiredDescriptionDefault
depthNo
venueYes
symbolYes

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?

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered; the description goes further by disclosing freshness signals the annotations cannot convey — feed status and book age — and the depth cap of 50 per side. It does not discuss rate limits, snapshot timing, or failure behavior when a feed is stale, which keeps it below a 5.

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?

Dense but front-loaded: the payload contents come first, then the two argument clarifications. Every clause carries information (output fields, symbol formats, depth semantics). Slightly run-on as a single sentence, but no filler to cut.

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?

For a 3-parameter, no-output-schema read tool, the description covers what is returned, how symbol and depth are interpreted, and freshness indicators. The remaining gap is venue validity — nothing says which venues exist or how to discover them — which the agent would need another tool for.

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 0%, so the description must carry the burden; it does well for symbol (accepts loose 'BTC'/'BTC-USDT'/'BTCUSDT' or exact Kalshi/Polymarket tickers) and depth ('per side, max 50'), which is real meaning beyond the bare integer schema. venue is left entirely unexplained — no list of accepted venues or case/format expectations — so one of three parameters remains undefined.

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?

Names a specific verb+resource (live order book) and constrains it to one symbol on one venue, then enumerates exactly what comes back (bids/asks as [price,size], best levels, mid, spread in absolute and bps, last trade, feed status, book age). The 'live' + 'one venue' framing separates it from the historical and consolidated siblings without opening their schemas.

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?

The scope phrase 'one symbol on one venue' effectively tells the agent this is the single-market snapshot path, and 'Live' implies the when (current state, not history). It stops short of naming alternatives such as the consolidated or historical book tools or stating exclusions, so usage is strongly implied rather than explicit.

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