Skip to main content
Glama

book_depth

Read-only

FREE, no key: the Taifoon venue's order book for one market as it stands: up to 40 bid and 40 ask levels (price, qty), the mid, the best bid and ask, the qty resting on each side, the largest resting levels as walls, and the venue clock (t_logical, unix seconds) with the age of the reading and whether it is stale. This is the VENUE's own book (its market-making and flow actors are synthetic), never CME order flow: say 'venue book' when you use it. For candles use tape; for the last close use price.

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": {
      "market": "<market>"
    },
    "name": "book_depth"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelsNolevels per side to return (default 10; the sums and walls always read all 40)
marketYesthe market

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, non-idempotent, non-destructive. The description adds genuinely useful context beyond them: the reading carries an age and a stale flag, the clock is t_logical in unix seconds, the actors are synthetic, and the data is the venue's own book rather than CME order flow. It does not address rate limits or how staleness should affect decisions, leaving room above a 4.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is a long run-on enumerating many fields, followed by a terminology instruction and a routing sentence. It is front-loaded with the key value, but the density costs readability.

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?

There is no output schema, but the description enumerates exactly what the response contains (levels, mid, best bid/ask, resting qty, walls, clock, age, staleness), so an agent knows what to expect. It is nearly complete for a simple read-only market data 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 baseline is 3. The description adds meaning: the sums and walls always read all 40 levels regardless of the levels parameter, which matters for interpreting the response even though the schema hints at it.

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?

Specific verb+resource: returns the venue's order book for one market and enumerates its contents (up to 40 bid/ask levels, mid, best bid/ask, resting qty per side, walls, venue clock with age and staleness). It distinguishes itself from siblings explicitly by naming tape for candles and price for the last close.

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

Usage Guidelines5/5

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

Names the alternatives and the condition selecting each: 'For candles use tape; for the last close use price.' It also scopes usage to one market and instructs the agent to call it the 'venue book' rather than CME flow.

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