whale-data

Order book

orderbook

Read-onlyIdempotent

The order book for one coin merged across exchanges: best bid and ask, the gap between them, and the dollars resting on each side with the exchanges holding each level.

Input Schema

TableJSON Schema

Name	Required	Description
`coin`	No	Coin symbol, e.g. BTC. A pair like ETH/USD works too.
`cursor`	No	Next page: the cursor from the previous answer.
`detail`	No	brief (default): the answer, key numbers and top rows. full: every row, paged with cursor.
`levels`	No	Price levels per side.

Output Schema

TableJSON Schema

Name	Required	Description
`as_of`	No	Data time, ISO.
`caveat`	No	A real limit, when non-null.
`cursor`	No	Next page (detail full).
`delayed`	No	Set when not live.
`summary`	No	The answer in one sentence.
`as_of_ms`	No	Data time, Unix ms.
`available`	No	False: no data; note says why.
`truncated`	No	Rows held back; see trimmed.
`next_tools`	No	Follow-up calls {tool,args,why}.
`access_note`	No	What this connection could not return.

Schema Changelog

Changes observed during successful MCP inspections.

Changed31 schema fields changedSep 24, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

addedInput schema / additionalProperties
```
Added value: +{}
```

changedInput schema / properties / coin / description

Previous value: -"Alias for pair."New value: +"Coin symbol, e.g. BTC. A pair like ETH/USD works too."

addedInput schema / properties / cursor

Added value: +{
+  "description": "Next page: the cursor from the previous answer.",
+  "type": "string"
+}

addedInput schema / properties / detail

Added value: +{
+  "description": "brief (default): the answer, key numbers and top rows. full: every row, paged with cursor.",
+  "enum": [
+    "brief",
+    "full"
+  ],
+  "type": "string"
+}

changedInput schema / properties / levels / description

Previous value: -"Price levels per side. Defaults to 10; the ceiling is 5 on the free plans, 10 on Starter, 25 on Pro (hard)."New value: +"Price levels per side."

removedInput schema / properties / levels / maximum
```
Removed value: -9007199254740991
```
removedInput schema / properties / levels / minimum
```
Removed value: --9007199254740991
```

removedInput schema / properties / pair

Removed value: -{
-  "description": "Trading pair, for example ETH/USD. A bare symbol like ETH is read as ETH/USD. Defaults to BTC/USD when omitted.",
-  "type": "string"
-}

removedOutput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

addedOutput schema / properties / access_note

Added value: +{
+  "description": "What this connection could not return."
+}

addedOutput schema / properties / as_of

Added value: +{
+  "description": "Data time, ISO."
+}

addedOutput schema / properties / as_of_ms

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Data time, Unix ms."
+}

removedOutput schema / properties / ask_usd_in_levels

Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Dollars resting on the ask side in the returned levels."
-}

removedOutput schema / properties / available / anyOf

Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]

changedOutput schema / properties / available / description

Previous value: -"False when the pair is not covered, not in the free set on this plan, or has no snapshot."New value: +"False: no data; note says why."

addedOutput schema / properties / available / type
```
Added value: +"boolean"
```

removedOutput schema / properties / best_ask

Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Best ask across venues."
-}

removedOutput schema / properties / best_bid

Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Best bid across venues."
-}

removedOutput schema / properties / bid_usd_in_levels

Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Dollars resting on the bid side in the returned levels."
-}

addedOutput schema / properties / caveat

Added value: +{
+  "description": "A real limit, when non-null."
+}

removedOutput schema / properties / combined

Removed value: -{
-  "anyOf": [
-    {
-      "additionalProperties": {},
-      "propertyNames": {
-        "type": "string"
-      },
-      "type": "object"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "bids and asks aggregated by price, each level listing the venues holding it."
-}

addedOutput schema / properties / cursor

Added value: +{
+  "description": "Next page (detail full)."
+}

addedOutput schema / properties / delayed

Added value: +{
+  "description": "Set when not live."
+}

removedOutput schema / properties / exchange_count

Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Venues merged."
-}

removedOutput schema / properties / levels

Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Levels per side returned."
-}

addedOutput schema / properties / next_tools

Added value: +{
+  "description": "Follow-up calls {tool,args,why}.",
+  "items": {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  },
+  "type": "array"
+}

removedOutput schema / properties / per_exchange

Removed value: -{
-  "anyOf": [
-    {
-      "additionalProperties": {},
-      "propertyNames": {
-        "type": "string"
-      },
-      "type": "object"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Each venue's own top levels."
-}

removedOutput schema / properties / spread_pct

Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Spread as a percent of the ask."
-}

changedOutput schema / properties / summary / description

Previous value: -"The answer in one plain sentence, computed from the fields below. Open the reply with this, then let the numbers back it up. Null only when there was nothing to summarise."New value: +"The answer in one sentence."

addedOutput schema / properties / truncated

Added value: +{
+  "description": "Rows held back; see trimmed."
+}

Changed1 schema field changedSep 15, 2026

changedInput schema / properties / levels / description

Previous value: -"Price levels per side. Defaults to 10; the ceiling is 5 keyless, 10 on Starter, 25 on Pro (hard)."New value: +"Price levels per side. Defaults to 10; the ceiling is 5 on the free plans, 10 on Starter, 25 on Pro (hard)."

AddedSep 5, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds meaningful context by disclosing that the data is merged across exchanges and showing exactly what is computed: bid/ask, spread, side dollar amounts, and holding exchanges. This goes beyond simply restating the annotations.

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

Conciseness5/5

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

A single densely informative sentence that front-loads the core subject ('order book for one coin merged across exchanges') and then lists the returned quantities in a natural order. There is no redundant wording or filler.

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 read-only tool with no required parameters and an output schema, the description plus schema covers the coin scope, aggregation behavior, and key returned items. The only real shortfall is explicit routing guidance among sibling tools, which was already penalized under usage guidelines.

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% and the schema already documents coin, cursor, detail, and levels. The description focuses on output content rather than parameter meaning, so it does not need to compensate for schema gaps; the baseline 3 applies.

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 clearly specifies the tool returns a consolidated per-coin order book and enumerates its key contents: best bid and ask, the gap, dollars resting on each side, and the exchanges at each level. It stops short of a 5 because it is a noun-phrase definition rather than a verb-led instruction and does not explicitly name sibling tools.

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?

The intended use is easy to infer: call this when the user wants a single coin's aggregated order book. However, there is no explicit when/when-not guidance or comparison to related tools such as market_now or coin_brief.

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

All whale-data tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?