Gate MCP

cex_spot_get_spot_candlesticks

Read-onlyIdempotent

Get candlestick/OHLCV data 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_candlesticks"
  }
}

Input Schema

Name	Required	Description	Default
`to`	No	End time of K-line in Unix timestamp (seconds). Defaults to current time if not specified
`from`	No	Start time of K-line in Unix timestamp (seconds). Defaults to to - 100 * interval if not specified
`limit`	No	Maximum number of data points to return. Mutually exclusive with from/to parameters
`interval`	No	Time interval of data points. Note: 30d represents natural month, not 30 days	30m
`currency_pair`	Yes	Currency pair

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 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: +"30m"
```
- addedInput schema / properties / interval / enum
```
Added value: +[
+  "1s",
+  "10s",
+  "1m",
+  "5m",
+  "15m",
+  "30m",
+  "1h",
+  "4h",
+  "8h",
+  "1d",
+  "7d",
+  "30d"
+]
```
- addedInput schema / properties / limit / default
```
Added value: +100
```
- addedInput schema / properties / limit / maximum
```
Added value: +1000
```
- changedInput schema / properties / limit / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / to / format
```
Added value: +"int64"
```
- changedInput schema / properties / to / type
```
Previous value: -"number"New value: +"integer"
```
Changed9 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: -"30m"
```
- removedInput schema / properties / interval / enum
```
Removed value: -[
-  "1s",
-  "10s",
-  "1m",
-  "5m",
-  "15m",
-  "30m",
-  "1h",
-  "4h",
-  "8h",
-  "1d",
-  "7d",
-  "30d"
-]
```
- removedInput schema / properties / limit / default
```
Removed value: -100
```
- removedInput schema / properties / limit / maximum
```
Removed value: -1000
```
- changedInput schema / properties / limit / type
```
Previous value: -"integer"New value: +"number"
```
- removedInput schema / properties / to / format
```
Removed value: -"int64"
```
- changedInput schema / properties / to / type
```
Previous value: -"integer"New value: +"number"
```
Changed9 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: +"30m"
```
- addedInput schema / properties / interval / enum
```
Added value: +[
+  "1s",
+  "10s",
+  "1m",
+  "5m",
+  "15m",
+  "30m",
+  "1h",
+  "4h",
+  "8h",
+  "1d",
+  "7d",
+  "30d"
+]
```
- addedInput schema / properties / limit / default
```
Added value: +100
```
- addedInput schema / properties / limit / maximum
```
Added value: +1000
```
- changedInput schema / properties / limit / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / to / format
```
Added value: +"int64"
```
- changedInput schema / properties / to / type
```
Previous value: -"number"New value: +"integer"
```
Changed9 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: -"30m"
```
- removedInput schema / properties / interval / enum
```
Removed value: -[
-  "1s",
-  "10s",
-  "1m",
-  "5m",
-  "15m",
-  "30m",
-  "1h",
-  "4h",
-  "8h",
-  "1d",
-  "7d",
-  "30d"
-]
```
- removedInput schema / properties / limit / default
```
Removed value: -100
```
- removedInput schema / properties / limit / maximum
```
Removed value: -1000
```
- changedInput schema / properties / limit / type
```
Previous value: -"integer"New value: +"number"
```
- removedInput schema / properties / to / format
```
Removed value: -"int64"
```
- changedInput schema / properties / to / type
```
Previous value: -"integer"New value: +"number"
```
Changed9 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: +"30m"
```
- addedInput schema / properties / interval / enum
```
Added value: +[
+  "1s",
+  "10s",
+  "1m",
+  "5m",
+  "15m",
+  "30m",
+  "1h",
+  "4h",
+  "8h",
+  "1d",
+  "7d",
+  "30d"
+]
```
- addedInput schema / properties / limit / default
```
Added value: +100
```
- addedInput schema / properties / limit / maximum
```
Added value: +1000
```
- changedInput schema / properties / limit / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / to / format
```
Added value: +"int64"
```
- changedInput schema / properties / to / type
```
Previous value: -"number"New value: +"integer"
```
Changed9 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: -"30m"
```
- removedInput schema / properties / interval / enum
```
Removed value: -[
-  "1s",
-  "10s",
-  "1m",
-  "5m",
-  "15m",
-  "30m",
-  "1h",
-  "4h",
-  "8h",
-  "1d",
-  "7d",
-  "30d"
-]
```
- removedInput schema / properties / limit / default
```
Removed value: -100
```
- removedInput schema / properties / limit / maximum
```
Removed value: -1000
```
- changedInput schema / properties / limit / type
```
Previous value: -"integer"New value: +"number"
```
- removedInput schema / properties / to / format
```
Removed value: -"int64"
```
- changedInput schema / properties / to / type
```
Previous value: -"integer"New value: +"number"
```
Changed9 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: +"30m"
```
- addedInput schema / properties / interval / enum
```
Added value: +[
+  "1s",
+  "10s",
+  "1m",
+  "5m",
+  "15m",
+  "30m",
+  "1h",
+  "4h",
+  "8h",
+  "1d",
+  "7d",
+  "30d"
+]
```
- addedInput schema / properties / limit / default
```
Added value: +100
```
- addedInput schema / properties / limit / maximum
```
Added value: +1000
```
- changedInput schema / properties / limit / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / to / format
```
Added value: +"int64"
```
- changedInput schema / properties / to / type
```
Previous value: -"number"New value: +"integer"
```
Changed9 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: -"30m"
```
- removedInput schema / properties / interval / enum
```
Removed value: -[
-  "1s",
-  "10s",
-  "1m",
-  "5m",
-  "15m",
-  "30m",
-  "1h",
-  "4h",
-  "8h",
-  "1d",
-  "7d",
-  "30d"
-]
```
- removedInput schema / properties / limit / default
```
Removed value: -100
```
- removedInput schema / properties / limit / maximum
```
Removed value: -1000
```
- changedInput schema / properties / limit / type
```
Previous value: -"integer"New value: +"number"
```
- removedInput schema / properties / to / format
```
Removed value: -"int64"
```
- changedInput schema / properties / to / type
```
Previous value: -"integer"New value: +"number"
```
Changed9 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: +"30m"
```
- addedInput schema / properties / interval / enum
```
Added value: +[
+  "1s",
+  "10s",
+  "1m",
+  "5m",
+  "15m",
+  "30m",
+  "1h",
+  "4h",
+  "8h",
+  "1d",
+  "7d",
+  "30d"
+]
```
- addedInput schema / properties / limit / default
```
Added value: +100
```
- addedInput schema / properties / limit / maximum
```
Added value: +1000
```
- changedInput schema / properties / limit / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / to / format
```
Added value: +"int64"
```
- changedInput schema / properties / to / type
```
Previous value: -"number"New value: +"integer"
```
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 safety is fully covered. The description adds nothing beyond that: no note on rate limits, history depth, or how the from/to versus limit exclusivity affects behavior (which lives only in the schema).

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 well-formed sentence with the resource front-loaded and no filler. It is efficient, though its brevity borders on under-specification for a 5-parameter market-data tool.

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?

With no output schema, the description should say something about the returned OHLCV shape or ordering; 'candlestick/OHLCV data' only gestures at it. The parameters and safety profile are otherwise fully covered by the schema and annotations, so nothing critical is missing.

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 defaults, an interval enum, and the from/to vs limit mutual-exclusion rule all documented in the schema. The description adds no further parameter meaning, so the baseline of 3 applies.

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?

The description gives a specific verb and resource ('Get candlestick/OHLCV data') scoped to a currency pair, so the operation is unambiguous. It does not, however, differentiate this spot tool from the many sibling candlestick tools (cex_dc_list_dc_candlesticks, cex_fx_get_fx_candlesticks, cex_options_list_options_candlesticks), leaving the market-type distinction to the tool name alone.

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 derivative-market candlestick siblings, nor any mention of prerequisites or exclusions. The agent must infer from the name prefix that this is the spot-market variant.

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.