Gate MCP

cex_dc_list_dc_candlesticks

Read-onlyIdempotent

List delivery candlesticks.

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

Input Schema

Name	Required	Description	Default
`to`	No	End timestamp in seconds
`from`	No	Start timestamp in seconds
`limit`	No	Maximum number of data points to return
`settle`	Yes	Settlement currency for delivery (e.g. usdt, btc)
`contract`	Yes	Delivery contract identifier (e.g. BTC_USDT; may use mark_/index_ prefix for price type)
`interval`	No	Time interval for data points	5m

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 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 / interval / default
```
Added value: +"5m"
```

addedInput schema / properties / interval / enum

Added value: +[
+  "10s",
+  "30s",
+  "1m",
+  "5m",
+  "15m",
+  "30m",
+  "1h",
+  "2h",
+  "4h",
+  "6h",
+  "8h",
+  "12h",
+  "1d",
+  "7d",
+  "1w",
+  "30d"
+]

addedInput schema / properties / limit / default
```
Added value: +100
```
addedInput schema / properties / limit / maximum
```
Added value: +2000
```

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"
+]

Changed11 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 / interval / default
```
Removed value: -"5m"
```

removedInput schema / properties / interval / enum

Removed value: -[
-  "10s",
-  "30s",
-  "1m",
-  "5m",
-  "15m",
-  "30m",
-  "1h",
-  "2h",
-  "4h",
-  "6h",
-  "8h",
-  "12h",
-  "1d",
-  "7d",
-  "1w",
-  "30d"
-]

removedInput schema / properties / limit / default
```
Removed value: -100
```
removedInput schema / properties / limit / maximum
```
Removed value: -2000
```

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"
+]

Changed11 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 / interval / default
```
Added value: +"5m"
```

addedInput schema / properties / interval / enum

Added value: +[
+  "10s",
+  "30s",
+  "1m",
+  "5m",
+  "15m",
+  "30m",
+  "1h",
+  "2h",
+  "4h",
+  "6h",
+  "8h",
+  "12h",
+  "1d",
+  "7d",
+  "1w",
+  "30d"
+]

addedInput schema / properties / limit / default
```
Added value: +100
```
addedInput schema / properties / limit / maximum
```
Added value: +2000
```

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"
+]

Changed11 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 / interval / default
```
Removed value: -"5m"
```

removedInput schema / properties / interval / enum

Removed value: -[
-  "10s",
-  "30s",
-  "1m",
-  "5m",
-  "15m",
-  "30m",
-  "1h",
-  "2h",
-  "4h",
-  "6h",
-  "8h",
-  "12h",
-  "1d",
-  "7d",
-  "1w",
-  "30d"
-]

removedInput schema / properties / limit / default
```
Removed value: -100
```
removedInput schema / properties / limit / maximum
```
Removed value: -2000
```

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"
+]

Changed11 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 / interval / default
```
Added value: +"5m"
```

addedInput schema / properties / interval / enum

Added value: +[
+  "10s",
+  "30s",
+  "1m",
+  "5m",
+  "15m",
+  "30m",
+  "1h",
+  "2h",
+  "4h",
+  "6h",
+  "8h",
+  "12h",
+  "1d",
+  "7d",
+  "1w",
+  "30d"
+]

addedInput schema / properties / limit / default
```
Added value: +100
```
addedInput schema / properties / limit / maximum
```
Added value: +2000
```

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"
+]

Changed11 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 / interval / default
```
Removed value: -"5m"
```

removedInput schema / properties / interval / enum

Removed value: -[
-  "10s",
-  "30s",
-  "1m",
-  "5m",
-  "15m",
-  "30m",
-  "1h",
-  "2h",
-  "4h",
-  "6h",
-  "8h",
-  "12h",
-  "1d",
-  "7d",
-  "1w",
-  "30d"
-]

removedInput schema / properties / limit / default
```
Removed value: -100
```
removedInput schema / properties / limit / maximum
```
Removed value: -2000
```

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"
+]

Changed11 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 / interval / default
```
Added value: +"5m"
```

addedInput schema / properties / interval / enum

Added value: +[
+  "10s",
+  "30s",
+  "1m",
+  "5m",
+  "15m",
+  "30m",
+  "1h",
+  "2h",
+  "4h",
+  "6h",
+  "8h",
+  "12h",
+  "1d",
+  "7d",
+  "1w",
+  "30d"
+]

addedInput schema / properties / limit / default
```
Added value: +100
```
addedInput schema / properties / limit / maximum
```
Added value: +2000
```

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"
+]

Changed11 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 / interval / default
```
Removed value: -"5m"
```

removedInput schema / properties / interval / enum

Removed value: -[
-  "10s",
-  "30s",
-  "1m",
-  "5m",
-  "15m",
-  "30m",
-  "1h",
-  "2h",
-  "4h",
-  "6h",
-  "8h",
-  "12h",
-  "1d",
-  "7d",
-  "1w",
-  "30d"
-]

removedInput schema / properties / limit / default
```
Removed value: -100
```
removedInput schema / properties / limit / maximum
```
Removed value: -2000
```

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"
+]

Changed11 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 / interval / default
```
Added value: +"5m"
```

addedInput schema / properties / interval / enum

Added value: +[
+  "10s",
+  "30s",
+  "1m",
+  "5m",
+  "15m",
+  "30m",
+  "1h",
+  "2h",
+  "4h",
+  "6h",
+  "8h",
+  "12h",
+  "1d",
+  "7d",
+  "1w",
+  "30d"
+]

addedInput schema / properties / limit / default
```
Added value: +100
```
addedInput schema / properties / limit / maximum
```
Added value: +2000
```

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=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered without prose. The description adds nothing beyond that - no note on pagination limits (limit max 2000), timestamp units, or whether mark_/index_ prefixed contracts are price-type variants rather than instruments.

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?

A single four-word sentence with no filler and the resource front-loaded after the verb, so nothing is wasteful. However, it is terse to the point of under-specification rather than efficiently informative.

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?

A six-parameter, two-required-parameter market-data query with an interval enum, a settlement-currency constraint, and no output schema needs more than this. The description supplies none of the context an agent needs to construct a correct call or interpret the response shape.

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 six parameters - including the from/to timestamp semantics, the interval enum, and the mark_/index_ contract prefix convention - are already documented in the schema. The description neither adds nor undermines that; 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 verb 'List' plus resource 'delivery candlesticks' identifies the operation, but 'delivery' is left undefined and there is no differentiation from the many sibling kline tools (cex_spot_get_spot_candlesticks, cex_fx_get_fx_candlesticks, cex_options_list_options_candlesticks). An agent could land here by name alone but couldn't justify choosing it over those alternatives.

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?

The description gives no when-to-use context, no prerequisites (required settle/contract), and no pointer to alternatives. With four or more candlestick tools in the sibling list, the absence of routing guidance is a real gap.

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.

cex_dc_list_dc_candlesticks

Tool call template

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources