Gate MCP

cex_dc_list_dc_trades

Read-onlyIdempotent

List delivery trades.

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_dc_list_dc_trades"
  }
}

Input Schema

Name	Required	Description
`to`	No	End timestamp in seconds
`from`	No	Start timestamp in seconds
`limit`	No	Maximum number of records to return
`settle`	Yes	Settlement currency for delivery (e.g. usdt, btc)
`last_id`	No	Specify list starting point using the last record ID from previous request
`contract`	Yes	Delivery contract identifier (e.g. BTC_USDT)

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedNov 2, 2026
- addedInput schema / properties / from / format
```
Added value: +"int64"
```
- changedInput schema / properties / from / type
```
Previous value: -"number"New value: +"integer"
```
- 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 / settle / enum
```
Added value: +[
+  "usdt"
+]
```
- addedInput schema / properties / to / format
```
Added value: +"int64"
```
- changedInput schema / properties / to / type
```
Previous value: -"number"New value: +"integer"
```
- changedInput schema / required
```
Previous value: -[
-  "contract"
-]New value: +[
+  "contract",
+  "settle"
+]
```
Changed10 schema fields changedOct 16, 2026
- removedInput schema / properties / from / format
```
Removed value: -"int64"
```
- changedInput schema / properties / from / type
```
Previous value: -"integer"New value: +"number"
```
- 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 / settle / enum
```
Removed value: -[
-  "usdt"
-]
```
- removedInput schema / properties / to / format
```
Removed value: -"int64"
```
- changedInput schema / properties / to / type
```
Previous value: -"integer"New value: +"number"
```
- changedInput schema / required
```
Previous value: -[
-  "contract",
-  "settle"
-]New value: +[
+  "contract"
+]
```
Changed10 schema fields changedOct 16, 2026
- addedInput schema / properties / from / format
```
Added value: +"int64"
```
- changedInput schema / properties / from / type
```
Previous value: -"number"New value: +"integer"
```
- 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 / settle / enum
```
Added value: +[
+  "usdt"
+]
```
- addedInput schema / properties / to / format
```
Added value: +"int64"
```
- changedInput schema / properties / to / type
```
Previous value: -"number"New value: +"integer"
```
- changedInput schema / required
```
Previous value: -[
-  "contract"
-]New value: +[
+  "contract",
+  "settle"
+]
```
Changed10 schema fields changedOct 16, 2026
- removedInput schema / properties / from / format
```
Removed value: -"int64"
```
- changedInput schema / properties / from / type
```
Previous value: -"integer"New value: +"number"
```
- 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 / settle / enum
```
Removed value: -[
-  "usdt"
-]
```
- removedInput schema / properties / to / format
```
Removed value: -"int64"
```
- changedInput schema / properties / to / type
```
Previous value: -"integer"New value: +"number"
```
- changedInput schema / required
```
Previous value: -[
-  "contract",
-  "settle"
-]New value: +[
+  "contract"
+]
```
Changed10 schema fields changedOct 16, 2026
- addedInput schema / properties / from / format
```
Added value: +"int64"
```
- changedInput schema / properties / from / type
```
Previous value: -"number"New value: +"integer"
```
- 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 / settle / enum
```
Added value: +[
+  "usdt"
+]
```
- addedInput schema / properties / to / format
```
Added value: +"int64"
```
- changedInput schema / properties / to / type
```
Previous value: -"number"New value: +"integer"
```
- changedInput schema / required
```
Previous value: -[
-  "contract"
-]New value: +[
+  "contract",
+  "settle"
+]
```
Changed10 schema fields changedOct 16, 2026
- removedInput schema / properties / from / format
```
Removed value: -"int64"
```
- changedInput schema / properties / from / type
```
Previous value: -"integer"New value: +"number"
```
- 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 / settle / enum
```
Removed value: -[
-  "usdt"
-]
```
- removedInput schema / properties / to / format
```
Removed value: -"int64"
```
- changedInput schema / properties / to / type
```
Previous value: -"integer"New value: +"number"
```
- changedInput schema / required
```
Previous value: -[
-  "contract",
-  "settle"
-]New value: +[
+  "contract"
+]
```
Changed10 schema fields changedOct 16, 2026
- addedInput schema / properties / from / format
```
Added value: +"int64"
```
- changedInput schema / properties / from / type
```
Previous value: -"number"New value: +"integer"
```
- 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 / settle / enum
```
Added value: +[
+  "usdt"
+]
```
- addedInput schema / properties / to / format
```
Added value: +"int64"
```
- changedInput schema / properties / to / type
```
Previous value: -"number"New value: +"integer"
```
- changedInput schema / required
```
Previous value: -[
-  "contract"
-]New value: +[
+  "contract",
+  "settle"
+]
```
Changed10 schema fields changedOct 16, 2026
- removedInput schema / properties / from / format
```
Removed value: -"int64"
```
- changedInput schema / properties / from / type
```
Previous value: -"integer"New value: +"number"
```
- 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 / settle / enum
```
Removed value: -[
-  "usdt"
-]
```
- removedInput schema / properties / to / format
```
Removed value: -"int64"
```
- changedInput schema / properties / to / type
```
Previous value: -"integer"New value: +"number"
```
- changedInput schema / required
```
Previous value: -[
-  "contract",
-  "settle"
-]New value: +[
+  "contract"
+]
```
Changed10 schema fields changedOct 16, 2026
- addedInput schema / properties / from / format
```
Added value: +"int64"
```
- changedInput schema / properties / from / type
```
Previous value: -"number"New value: +"integer"
```
- 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 / settle / enum
```
Added value: +[
+  "usdt"
+]
```
- addedInput schema / properties / to / format
```
Added value: +"int64"
```
- changedInput schema / properties / to / type
```
Previous value: -"number"New value: +"integer"
```
- changedInput schema / required
```
Previous value: -[
-  "contract"
-]New value: +[
+  "contract",
+  "settle"
+]
```
First observedApr 16, 2026

TDQS

C2.5/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 covered. The description adds nothing beyond them — no note on pagination via last_id, rate limits, or the fact that results are scoped to a single contract and settlement currency.

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

Conciseness3/5

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

It is a single four-word sentence with zero waste and is front-loaded, but at that length it is under-specified rather than efficient; there is no second sentence earning its place or absent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter, two-required listing tool with no output schema, the description should at least say what a delivery trade record contains and how paging works. None of that is present, so an agent cannot fully predict what it will get back or how to page.

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% and each of the six parameters carries its own description (timestamps in seconds, limit max 1000, settle enum, last_id cursor). The description contributes no additional meaning, which is acceptable given the schema does the work — baseline 3.

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 verb and a resource ("List" + "delivery trades") that maps the '_dc_' segment to the delivery market, so an agent gets the gist. But it is essentially the tool name restated and offers no differentiation from the many trade-listing siblings such as cex_options_list_options_trades or cex_fx_get_fx_trades.

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 statement of when to call this versus the sibling trade/contract listing tools, and no mention of prerequisites like needing a valid delivery contract. The agent must infer scope entirely from the name and the required 'contract'/'settle' params.

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.