Gate MCP

cex_fx_list_fx_contracts

Read-onlyIdempotent

List all perpetual futures contracts

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

Input Schema

Name	Required	Description
`limit`	No	Maximum number of records to return
`offset`	No	List offset, starting from 0
`settle`	Yes	Settlement currency

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedNov 2, 2026
- addedInput schema / properties / limit / default
```
Added value: +100
```
- addedInput schema / properties / limit / maximum
```
Added value: +1000
```
- addedInput schema / properties / limit / minimum
```
Added value: +1
```
- changedInput schema / properties / limit / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / offset / default
```
Added value: +0
```
- addedInput schema / properties / offset / minimum
```
Added value: +0
```
- changedInput schema / properties / offset / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / settle / enum
```
Added value: +[
+  "btc",
+  "usdt",
+  "usd1"
+]
```
- addedInput schema / required
```
Added value: +[
+  "settle"
+]
```
Changed9 schema fields changedOct 16, 2026
- removedInput schema / properties / limit / default
```
Removed value: -100
```
- removedInput schema / properties / limit / maximum
```
Removed value: -1000
```
- removedInput schema / properties / limit / minimum
```
Removed value: -1
```
- changedInput schema / properties / limit / type
```
Previous value: -"integer"New value: +"number"
```
- removedInput schema / properties / offset / default
```
Removed value: -0
```
- removedInput schema / properties / offset / minimum
```
Removed value: -0
```
- changedInput schema / properties / offset / type
```
Previous value: -"integer"New value: +"number"
```
- removedInput schema / properties / settle / enum
```
Removed value: -[
-  "btc",
-  "usdt",
-  "usd1"
-]
```
- removedInput schema / required
```
Removed value: -[
-  "settle"
-]
```
Changed9 schema fields changedOct 16, 2026
- addedInput schema / properties / limit / default
```
Added value: +100
```
- addedInput schema / properties / limit / maximum
```
Added value: +1000
```
- addedInput schema / properties / limit / minimum
```
Added value: +1
```
- changedInput schema / properties / limit / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / offset / default
```
Added value: +0
```
- addedInput schema / properties / offset / minimum
```
Added value: +0
```
- changedInput schema / properties / offset / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / settle / enum
```
Added value: +[
+  "btc",
+  "usdt",
+  "usd1"
+]
```
- addedInput schema / required
```
Added value: +[
+  "settle"
+]
```
Changed9 schema fields changedOct 16, 2026
- removedInput schema / properties / limit / default
```
Removed value: -100
```
- removedInput schema / properties / limit / maximum
```
Removed value: -1000
```
- removedInput schema / properties / limit / minimum
```
Removed value: -1
```
- changedInput schema / properties / limit / type
```
Previous value: -"integer"New value: +"number"
```
- removedInput schema / properties / offset / default
```
Removed value: -0
```
- removedInput schema / properties / offset / minimum
```
Removed value: -0
```
- changedInput schema / properties / offset / type
```
Previous value: -"integer"New value: +"number"
```
- removedInput schema / properties / settle / enum
```
Removed value: -[
-  "btc",
-  "usdt",
-  "usd1"
-]
```
- removedInput schema / required
```
Removed value: -[
-  "settle"
-]
```
Changed9 schema fields changedOct 16, 2026
- addedInput schema / properties / limit / default
```
Added value: +100
```
- addedInput schema / properties / limit / maximum
```
Added value: +1000
```
- addedInput schema / properties / limit / minimum
```
Added value: +1
```
- changedInput schema / properties / limit / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / offset / default
```
Added value: +0
```
- addedInput schema / properties / offset / minimum
```
Added value: +0
```
- changedInput schema / properties / offset / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / settle / enum
```
Added value: +[
+  "btc",
+  "usdt",
+  "usd1"
+]
```
- addedInput schema / required
```
Added value: +[
+  "settle"
+]
```
Changed9 schema fields changedOct 16, 2026
- removedInput schema / properties / limit / default
```
Removed value: -100
```
- removedInput schema / properties / limit / maximum
```
Removed value: -1000
```
- removedInput schema / properties / limit / minimum
```
Removed value: -1
```
- changedInput schema / properties / limit / type
```
Previous value: -"integer"New value: +"number"
```
- removedInput schema / properties / offset / default
```
Removed value: -0
```
- removedInput schema / properties / offset / minimum
```
Removed value: -0
```
- changedInput schema / properties / offset / type
```
Previous value: -"integer"New value: +"number"
```
- removedInput schema / properties / settle / enum
```
Removed value: -[
-  "btc",
-  "usdt",
-  "usd1"
-]
```
- removedInput schema / required
```
Removed value: -[
-  "settle"
-]
```
Changed9 schema fields changedOct 16, 2026
- addedInput schema / properties / limit / default
```
Added value: +100
```
- addedInput schema / properties / limit / maximum
```
Added value: +1000
```
- addedInput schema / properties / limit / minimum
```
Added value: +1
```
- changedInput schema / properties / limit / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / offset / default
```
Added value: +0
```
- addedInput schema / properties / offset / minimum
```
Added value: +0
```
- changedInput schema / properties / offset / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / settle / enum
```
Added value: +[
+  "btc",
+  "usdt",
+  "usd1"
+]
```
- addedInput schema / required
```
Added value: +[
+  "settle"
+]
```
Changed9 schema fields changedOct 16, 2026
- removedInput schema / properties / limit / default
```
Removed value: -100
```
- removedInput schema / properties / limit / maximum
```
Removed value: -1000
```
- removedInput schema / properties / limit / minimum
```
Removed value: -1
```
- changedInput schema / properties / limit / type
```
Previous value: -"integer"New value: +"number"
```
- removedInput schema / properties / offset / default
```
Removed value: -0
```
- removedInput schema / properties / offset / minimum
```
Removed value: -0
```
- changedInput schema / properties / offset / type
```
Previous value: -"integer"New value: +"number"
```
- removedInput schema / properties / settle / enum
```
Removed value: -[
-  "btc",
-  "usdt",
-  "usd1"
-]
```
- removedInput schema / required
```
Removed value: -[
-  "settle"
-]
```
Changed9 schema fields changedOct 16, 2026
- addedInput schema / properties / limit / default
```
Added value: +100
```
- addedInput schema / properties / limit / maximum
```
Added value: +1000
```
- addedInput schema / properties / limit / minimum
```
Added value: +1
```
- changedInput schema / properties / limit / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / offset / default
```
Added value: +0
```
- addedInput schema / properties / offset / minimum
```
Added value: +0
```
- changedInput schema / properties / offset / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / settle / enum
```
Added value: +[
+  "btc",
+  "usdt",
+  "usd1"
+]
```
- addedInput schema / required
```
Added value: +[
+  "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, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered. The description adds nothing beyond that: no mention that settle is mandatory, no pagination behavior, no note that this is public market reference data. It is a pure restatement of the name.

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, which is the right shape for a simple list endpoint. It is under-specified rather than bloated, which is penalized in other dimensions, not this one.

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 three-parameter read-only listing with full schema coverage and annotations, the minimum viable information is present. The critical missing piece is differentiation from cex_fx_list_fx_contracts_all, since an agent choosing between the two has nothing in the description to decide with.

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% with three documented parameters including an enum for settle, so the schema carries the load and baseline 3 applies. The description adds no semantic value beyond the schema and arguably misleads by saying 'all' despite a required settle filter.

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: 'List all perpetual futures contracts'. Clear on its own, but it makes no attempt to distinguish itself from the very similar sibling cex_fx_list_fx_contracts_all, and the word 'all' sits oddly against a mandatory settlement-currency filter.

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 cex_fx_list_fx_contracts_all, cex_fx_get_fx_contract, or the cfd/dc/options contract listings. No prerequisites, exclusions, or selection criteria are given, so the agent must infer everything from the tool 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.