Skip to main content
Glama

Order book walls

order_book_walls
Read-only

Large resting limit orders ("walls") in the order book within ±range_pct of the price, sorted by size in USD. source "binance" = Binance spot book; "all" = 15 books from 10 exchanges aggregated (Binance, OKX, Bybit, Kraken, Bitfinex, Coinbase, Bitstamp, Gemini, Deribit, Gate).

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": {
      "pair": "<pair>"
    },
    "name": "order_book_walls"
  }
}

Input Schema

NameRequiredDescriptionDefault
pairYesCoin traded against USDT: BTC, ETH, SOL, XRP, BNB, DOGE, ZEC or NEAR
limitNoMaximum number of walls to return (1 to 50)
sourceNo"binance" = Binance spot book only; "all" = 15 books from 10 exchanges aggregatedbinance
range_pctNoHow far from the price to look, in % (0.1 to 30)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real behavioral detail beyond that — results are sorted by size in USD and 'all' aggregates 15 books across 10 exchanges — but it never states what qualifies as a 'large' wall (size threshold) or whether thin books yield fewer results, which matters for interpreting output.

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?

Two sentences, front-loaded with the definition and scope, then the source modes. Dense and largely free of waste, though the source explanation duplicates the schema's enum descriptions almost verbatim.

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?

With four fully documented parameters, no output schema, and readOnly annotations, the definition covers what the tool returns (walls sorted by size in USD, capped by limit) and how scope is bounded. The main remaining gap is the undefined 'large' threshold, which affects how the agent should interpret an empty or short result.

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 coverage is 100%, so every parameter including enums already carries a description. The description essentially restates the source semantics and range scoping rather than adding new meaning such as format, precision, or how range_pct interacts with limit. Baseline 3 applies when the schema does the heavy lifting.

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 names the specific resource (large resting limit orders, i.e. 'walls') and its scope (within ±range_pct of the price, sorted by size in USD), which is far more specific than the title alone. It implicitly separates itself from big_trades by emphasizing resting orders rather than executions, but it never explicitly contrasts with any sibling tool.

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?

Usage context is only implied: the reader infers this is for finding liquidity walls rather than executed volume. The source explanation ('binance' vs 'all' = 15 books from 10 exchanges) helps the agent choose a mode, but there is no when-to-use/when-not guidance and no named alternative among big_trades, candles, cvd, futures, or market_snapshot.

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