Gate MCP

cex_options_list_options_candlesticks

Read-onlyIdempotent

Get options candlestick data

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>"
    },
    "name": "cex_options_list_options_candlesticks"
  }
}

Input Schema

Name	Required	Description	Default
`to`	No	End timestamp in seconds
`from`	No	Start timestamp in seconds
`limit`	No	Maximum number of records to return
`contract`	Yes	Options contract name
`interval`	No	Time interval between data points, e.g. 1m, 5m, 15m, 30m, 1h	5m

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 / interval / default
```
Added value: +"5m"
```
- addedInput schema / properties / interval / enum
```
Added value: +[
+  "1m",
+  "5m",
+  "15m",
+  "30m",
+  "1h"
+]
```
- 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 / to / format
```
Added value: +"int64"
```
- changedInput schema / properties / to / type
```
Previous value: -"number"New value: +"integer"
```
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 / interval / default
```
Removed value: -"5m"
```
- removedInput schema / properties / interval / enum
```
Removed value: -[
-  "1m",
-  "5m",
-  "15m",
-  "30m",
-  "1h"
-]
```
- 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 / to / format
```
Removed value: -"int64"
```
- changedInput schema / properties / to / type
```
Previous value: -"integer"New value: +"number"
```
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 / interval / default
```
Added value: +"5m"
```
- addedInput schema / properties / interval / enum
```
Added value: +[
+  "1m",
+  "5m",
+  "15m",
+  "30m",
+  "1h"
+]
```
- 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 / to / format
```
Added value: +"int64"
```
- changedInput schema / properties / to / type
```
Previous value: -"number"New value: +"integer"
```
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 / interval / default
```
Removed value: -"5m"
```
- removedInput schema / properties / interval / enum
```
Removed value: -[
-  "1m",
-  "5m",
-  "15m",
-  "30m",
-  "1h"
-]
```
- 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 / to / format
```
Removed value: -"int64"
```
- changedInput schema / properties / to / type
```
Previous value: -"integer"New value: +"number"
```
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 / interval / default
```
Added value: +"5m"
```
- addedInput schema / properties / interval / enum
```
Added value: +[
+  "1m",
+  "5m",
+  "15m",
+  "30m",
+  "1h"
+]
```
- 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 / to / format
```
Added value: +"int64"
```
- changedInput schema / properties / to / type
```
Previous value: -"number"New value: +"integer"
```
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 / interval / default
```
Removed value: -"5m"
```
- removedInput schema / properties / interval / enum
```
Removed value: -[
-  "1m",
-  "5m",
-  "15m",
-  "30m",
-  "1h"
-]
```
- 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 / to / format
```
Removed value: -"int64"
```
- changedInput schema / properties / to / type
```
Previous value: -"integer"New value: +"number"
```
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 / interval / default
```
Added value: +"5m"
```
- addedInput schema / properties / interval / enum
```
Added value: +[
+  "1m",
+  "5m",
+  "15m",
+  "30m",
+  "1h"
+]
```
- 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 / to / format
```
Added value: +"int64"
```
- changedInput schema / properties / to / type
```
Previous value: -"number"New value: +"integer"
```
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 / interval / default
```
Removed value: -"5m"
```
- removedInput schema / properties / interval / enum
```
Removed value: -[
-  "1m",
-  "5m",
-  "15m",
-  "30m",
-  "1h"
-]
```
- 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 / to / format
```
Removed value: -"int64"
```
- changedInput schema / properties / to / type
```
Previous value: -"integer"New value: +"number"
```
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 / interval / default
```
Added value: +"5m"
```
- addedInput schema / properties / interval / enum
```
Added value: +[
+  "1m",
+  "5m",
+  "15m",
+  "30m",
+  "1h"
+]
```
- 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 / to / format
```
Added value: +"int64"
```
- changedInput schema / properties / to / type
```
Previous value: -"number"New value: +"integer"
```
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 that: no note on rate limits, data granularity behavior (e.g. how from/to interact with interval), or default lookback when timestamps are omitted.

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 five-word sentence with zero waste, but the brevity reflects under-specification rather than disciplined conciseness. There is no front-loaded scoping or qualifying detail to orient the agent.

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 five-parameter market-data tool with no output schema and no annotations covering return shape, the description should say what a candle record looks like and how from/to/interval combine. It also fails to disambiguate the required 'contract' parameter from the underlying-candlestick sibling, leaving a real risk of wrong-tool selection.

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 every parameter (contract, from, to, interval, limit) is documented in the schema itself, justifying the baseline 3. The description contributes no additional semantics such as the contract naming convention or interval timestamp alignment.

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 names a specific resource ('options candlestick data') with a generic verb ('Get'), so the agent knows roughly what it returns. However, it does not distinguish this from the close sibling cex_options_list_options_underlying_candlesticks, which could easily be confused with options-contract candlesticks.

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 underlying-candlesticks sibling, the spot/fx candlestick variants, or the options tickers/trades tools. No prerequisites, no exclusions, no recommended flow.

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.