Gate MCP

cex_fx_get_fx_order_book

Read-onlyIdempotent

Get futures order book

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": {
      "contract": "<contract>",
      "settle": "<settle>"
    },
    "name": "cex_fx_get_fx_order_book"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of order depth levels to return
`settle`	Yes	Settlement currency
`with_id`	No	Whether to return order book update ID. ID increments by 1 on each change
`contract`	Yes	Futures contract name
`interval`	No	Order depth aggregation precision. 0 means no aggregation, defaults to 0 if not specified	0

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 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 / maximum
```
Added value: +50
```
- addedInput schema / properties / limit / minimum
```
Added value: +1
```
- changedInput schema / properties / limit / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / settle / enum
```
Added value: +[
+  "btc",
+  "usdt",
+  "usd1"
+]
```
- addedInput schema / properties / with_id / default
```
Added value: +false
```
- changedInput schema / required
```
Previous value: -[
-  "contract"
-]New value: +[
+  "contract",
+  "settle"
+]
```
Changed8 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 / maximum
```
Removed value: -50
```
- removedInput schema / properties / limit / minimum
```
Removed value: -1
```
- changedInput schema / properties / limit / type
```
Previous value: -"integer"New value: +"number"
```
- removedInput schema / properties / settle / enum
```
Removed value: -[
-  "btc",
-  "usdt",
-  "usd1"
-]
```
- removedInput schema / properties / with_id / default
```
Removed value: -false
```
- changedInput schema / required
```
Previous value: -[
-  "contract",
-  "settle"
-]New value: +[
+  "contract"
+]
```
Changed8 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 / maximum
```
Added value: +50
```
- addedInput schema / properties / limit / minimum
```
Added value: +1
```
- changedInput schema / properties / limit / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / settle / enum
```
Added value: +[
+  "btc",
+  "usdt",
+  "usd1"
+]
```
- addedInput schema / properties / with_id / default
```
Added value: +false
```
- changedInput schema / required
```
Previous value: -[
-  "contract"
-]New value: +[
+  "contract",
+  "settle"
+]
```
Changed8 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 / maximum
```
Removed value: -50
```
- removedInput schema / properties / limit / minimum
```
Removed value: -1
```
- changedInput schema / properties / limit / type
```
Previous value: -"integer"New value: +"number"
```
- removedInput schema / properties / settle / enum
```
Removed value: -[
-  "btc",
-  "usdt",
-  "usd1"
-]
```
- removedInput schema / properties / with_id / default
```
Removed value: -false
```
- changedInput schema / required
```
Previous value: -[
-  "contract",
-  "settle"
-]New value: +[
+  "contract"
+]
```
Changed8 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 / maximum
```
Added value: +50
```
- addedInput schema / properties / limit / minimum
```
Added value: +1
```
- changedInput schema / properties / limit / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / settle / enum
```
Added value: +[
+  "btc",
+  "usdt",
+  "usd1"
+]
```
- addedInput schema / properties / with_id / default
```
Added value: +false
```
- changedInput schema / required
```
Previous value: -[
-  "contract"
-]New value: +[
+  "contract",
+  "settle"
+]
```
Changed8 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 / maximum
```
Removed value: -50
```
- removedInput schema / properties / limit / minimum
```
Removed value: -1
```
- changedInput schema / properties / limit / type
```
Previous value: -"integer"New value: +"number"
```
- removedInput schema / properties / settle / enum
```
Removed value: -[
-  "btc",
-  "usdt",
-  "usd1"
-]
```
- removedInput schema / properties / with_id / default
```
Removed value: -false
```
- changedInput schema / required
```
Previous value: -[
-  "contract",
-  "settle"
-]New value: +[
+  "contract"
+]
```
Changed8 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 / maximum
```
Added value: +50
```
- addedInput schema / properties / limit / minimum
```
Added value: +1
```
- changedInput schema / properties / limit / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / settle / enum
```
Added value: +[
+  "btc",
+  "usdt",
+  "usd1"
+]
```
- addedInput schema / properties / with_id / default
```
Added value: +false
```
- changedInput schema / required
```
Previous value: -[
-  "contract"
-]New value: +[
+  "contract",
+  "settle"
+]
```
Changed8 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 / maximum
```
Removed value: -50
```
- removedInput schema / properties / limit / minimum
```
Removed value: -1
```
- changedInput schema / properties / limit / type
```
Previous value: -"integer"New value: +"number"
```
- removedInput schema / properties / settle / enum
```
Removed value: -[
-  "btc",
-  "usdt",
-  "usd1"
-]
```
- removedInput schema / properties / with_id / default
```
Removed value: -false
```
- changedInput schema / required
```
Previous value: -[
-  "contract",
-  "settle"
-]New value: +[
+  "contract"
+]
```
Changed8 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 / maximum
```
Added value: +50
```
- addedInput schema / properties / limit / minimum
```
Added value: +1
```
- changedInput schema / properties / limit / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / settle / enum
```
Added value: +[
+  "btc",
+  "usdt",
+  "usd1"
+]
```
- addedInput schema / properties / with_id / default
```
Added value: +false
```
- changedInput schema / required
```
Previous value: -[
-  "contract"
-]New value: +[
+  "contract",
+  "settle"
+]
```
First observedApr 16, 2026

TDQS

C2.9/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: it does not describe snapshot semantics, whether updates are pushed, aggregation/interval behavior, or typical depth/volume of the returned book.

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 short, front-loaded sentence with zero waste. It is perhaps too terse for the tool's complexity, but it is not verbose or poorly structured.

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 five-parameter market-data tool with no output schema, the description is minimally adequate: annotations cover safety and the schema covers inputs. However, it does not explain the shape of an order book response (bids/asks/levels) or how interval aggregation and with_id affect output, leaving meaningful gaps.

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 all five parameters (limit, settle, with_id, contract, interval) are documented in the schema itself. The description adds no parameter meaning, which is acceptable at this coverage level but provides no extra value.

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?

States a specific verb and resource ('Get futures order book'), and 'futures' distinguishes it from spot/options order book siblings. It does not distinguish it from cex_fx_list_fx_rpi_order_book, the other futures order-book tool in the same family, so sibling differentiation is incomplete.

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 guidance on when to use this versus the RPI futures order book, spot order book, options order book, or stock order book siblings. No prerequisites or exclusions are stated; the agent must infer selection from the tool name alone.

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.