Skip to main content
Glama

AINDEX

Order books across venues

order_books
Read-only

One market's order books on Lighter on Robinhood Chain, Hyperliquid, Binance and Bybit, read the same way: spread, dollars within 0.5, 1 and 2% each side, which side is heavier, what a $10k, $100k and $1M market order would pay, and the walls (largest 0.1% bins), merged across venues.

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": "order_books"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds real value by disclosing that results are merged across four venues and that several values are derived (depth bands, $10k/$100k/$1M market-order cost, 0.1% walls). It says nothing about latency, snapshot freshness, or what happens when one venue is unavailable — relevant for a fan-out query across four exchanges.

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?

One tightly packed sentence with no filler; the venue list and derived metrics are front-loaded and every clause carries content. The mid-sentence list of spread, depth percentages and notional sizes is dense enough that a structured breakdown would scan faster, but nothing is redundant.

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

Completeness3/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 correctly shoulders the burden of describing return contents and does so thoroughly. However, the missing symbol-format guidance and the absence of any note on aggregation timing or partial-venue failure leave gaps for a one-parameter, multi-venue fan-out tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%: the single required `symbol` parameter has only a regex pattern and no prose, and the description never mentions `symbol` at all. The pattern permits ':', '/', '=', '_' and '-', so venue-qualified or pair-style formats are plausible but unexplained, leaving the agent to guess the accepted symbol form.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description makes the resource and scope concrete: order book metrics for one market aggregated across Lighter/Robinhood Chain, Hyperliquid, Binance and Bybit, with a specific metric list (spread, depth bands, imbalance, market-order cost, walls). An agent can tell this is a cross-venue book snapshot tool. It never names a sibling such as get_spreads or get_levels, so the boundary against the lighter-weight book tools is left implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, no mention of alternatives, and no prerequisites or cost/precision tradeoffs versus a spread-only or raw-levels tool. The agent must infer the selection criteria entirely from the output list.

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