Gate MCP

cex_spot_get_spot_order_book

Read-onlyIdempotent

Get the order book for a currency pair

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": {
      "currency_pair": "<currency_pair>"
    },
    "name": "cex_spot_get_spot_order_book"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of order depth levels to return, default 10, max 100
`with_id`	No	Whether to return order book update ID
`interval`	No	Order depth aggregation precision. 0 means no aggregation	0
`currency_pair`	Yes	Currency pair

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 2, 2026
- addedInput schema / properties / interval / default
```
Added value: +"0"
```
- addedInput schema / properties / limit / default
```
Added value: +10
```
- addedInput schema / properties / limit / minimum
```
Added value: +1
```
- changedInput schema / properties / limit / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / with_id / default
```
Added value: +false
```
Changed5 schema fields changedOct 16, 2026
- removedInput schema / properties / interval / default
```
Removed value: -"0"
```
- removedInput schema / properties / limit / default
```
Removed value: -10
```
- removedInput schema / properties / limit / minimum
```
Removed value: -1
```
- changedInput schema / properties / limit / type
```
Previous value: -"integer"New value: +"number"
```
- removedInput schema / properties / with_id / default
```
Removed value: -false
```
Changed5 schema fields changedOct 16, 2026
- addedInput schema / properties / interval / default
```
Added value: +"0"
```
- addedInput schema / properties / limit / default
```
Added value: +10
```
- addedInput schema / properties / limit / minimum
```
Added value: +1
```
- changedInput schema / properties / limit / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / with_id / default
```
Added value: +false
```
Changed5 schema fields changedOct 16, 2026
- removedInput schema / properties / interval / default
```
Removed value: -"0"
```
- removedInput schema / properties / limit / default
```
Removed value: -10
```
- removedInput schema / properties / limit / minimum
```
Removed value: -1
```
- changedInput schema / properties / limit / type
```
Previous value: -"integer"New value: +"number"
```
- removedInput schema / properties / with_id / default
```
Removed value: -false
```
Changed5 schema fields changedOct 16, 2026
- addedInput schema / properties / interval / default
```
Added value: +"0"
```
- addedInput schema / properties / limit / default
```
Added value: +10
```
- addedInput schema / properties / limit / minimum
```
Added value: +1
```
- changedInput schema / properties / limit / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / with_id / default
```
Added value: +false
```
Changed5 schema fields changedOct 16, 2026
- removedInput schema / properties / interval / default
```
Removed value: -"0"
```
- removedInput schema / properties / limit / default
```
Removed value: -10
```
- removedInput schema / properties / limit / minimum
```
Removed value: -1
```
- changedInput schema / properties / limit / type
```
Previous value: -"integer"New value: +"number"
```
- removedInput schema / properties / with_id / default
```
Removed value: -false
```
Changed5 schema fields changedOct 16, 2026
- addedInput schema / properties / interval / default
```
Added value: +"0"
```
- addedInput schema / properties / limit / default
```
Added value: +10
```
- addedInput schema / properties / limit / minimum
```
Added value: +1
```
- changedInput schema / properties / limit / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / with_id / default
```
Added value: +false
```
Changed5 schema fields changedOct 16, 2026
- removedInput schema / properties / interval / default
```
Removed value: -"0"
```
- removedInput schema / properties / limit / default
```
Removed value: -10
```
- removedInput schema / properties / limit / minimum
```
Removed value: -1
```
- changedInput schema / properties / limit / type
```
Previous value: -"integer"New value: +"number"
```
- removedInput schema / properties / with_id / default
```
Removed value: -false
```
Changed5 schema fields changedOct 16, 2026
- addedInput schema / properties / interval / default
```
Added value: +"0"
```
- addedInput schema / properties / limit / default
```
Added value: +10
```
- addedInput schema / properties / limit / minimum
```
Added value: +1
```
- changedInput schema / properties / limit / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / with_id / default
```
Added value: +false
```
First observedApr 16, 2026

TDQS

C2.7/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: no rate-limit behavior, no note on snapshot vs streaming, no indication of how deep/large the response is or whether depth is aggregated.

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?

A single front-loaded sentence with zero filler. It is efficient, though its brevity edges toward under-specification rather than tight communication.

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?

For a simple 4-parameter read with full schema coverage and rich annotations, the essentials are present. However, with no output schema the description should at least indicate that the result is bids/asks depth, which it omits.

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 100%, so limit, with_id, interval, and currency_pair are all self-documented. The description contributes no additional semantics (e.g., how interval interacts with limit, or the cost of large limits), so the baseline 3 applies.

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

Purpose3/5

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

The description gives a specific verb and resource ('Get the order book'), but with siblings like cex_fx_get_fx_order_book, cex_dc_list_dc_order_book, cex_options_list_options_order_book, and cex_spot_list_spot_rpi_order_book, the description alone never states this is the spot market or how it differs from those. An agent must infer the scope from the tool name rather than the description.

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?

No guidance on when to use this versus the RPI order book variant or any derivative-market order book sibling, and no mention of prerequisites or typical use cases. The agent gets no routing signal beyond the name.

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

All Gate MCP 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.