Skip to main content
Glama

cex_fx_get_fx_candlesticks

Read-onlyIdempotent

Get futures candlestick/OHLCV 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>",
      "settle": "<settle>"
    },
    "name": "cex_fx_get_fx_candlesticks"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnd timestamp in seconds, defaults to current time if not specified
fromNoStart timestamp in seconds. Defaults to to - 100 * interval if not specified
limitNoMaximum number of data points to return. Mutually exclusive with from/to parameters
settleYesSettlement currency
contractYesFutures contract name
intervalNoTime interval. Note: 1w means natural week, 7d aligns with Unix epoch, 30d means natural month5m
timezoneNoTimezone: all/utc0/utc8, defaults to utc0utc0

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • 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",
      +  "1m",
      +  "5m",
      +  "15m",
      +  "30m",
      +  "1h",
      +  "4h",
      +  "8h",
      +  "1d",
      +  "7d"
      +]
    • 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: +[
      +  "btc",
      +  "usdt",
      +  "usd1"
      +]
    • addedInput schema / properties / timezone / default
      Added value: +"utc0"
    • 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"
      +]
  2. Changed12 schema fields changed
    • 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",
      -  "1m",
      -  "5m",
      -  "15m",
      -  "30m",
      -  "1h",
      -  "4h",
      -  "8h",
      -  "1d",
      -  "7d"
      -]
    • 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: -[
      -  "btc",
      -  "usdt",
      -  "usd1"
      -]
    • removedInput schema / properties / timezone / default
      Removed value: -"utc0"
    • 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"
      +]
  3. Changed12 schema fields changed
    • 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",
      +  "1m",
      +  "5m",
      +  "15m",
      +  "30m",
      +  "1h",
      +  "4h",
      +  "8h",
      +  "1d",
      +  "7d"
      +]
    • 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: +[
      +  "btc",
      +  "usdt",
      +  "usd1"
      +]
    • addedInput schema / properties / timezone / default
      Added value: +"utc0"
    • 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"
      +]
  4. Changed12 schema fields changed
    • 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",
      -  "1m",
      -  "5m",
      -  "15m",
      -  "30m",
      -  "1h",
      -  "4h",
      -  "8h",
      -  "1d",
      -  "7d"
      -]
    • 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: -[
      -  "btc",
      -  "usdt",
      -  "usd1"
      -]
    • removedInput schema / properties / timezone / default
      Removed value: -"utc0"
    • 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"
      +]
  5. Changed12 schema fields changed
    • 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",
      +  "1m",
      +  "5m",
      +  "15m",
      +  "30m",
      +  "1h",
      +  "4h",
      +  "8h",
      +  "1d",
      +  "7d"
      +]
    • 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: +[
      +  "btc",
      +  "usdt",
      +  "usd1"
      +]
    • addedInput schema / properties / timezone / default
      Added value: +"utc0"
    • 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"
      +]
  6. Changed12 schema fields changed
    • 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",
      -  "1m",
      -  "5m",
      -  "15m",
      -  "30m",
      -  "1h",
      -  "4h",
      -  "8h",
      -  "1d",
      -  "7d"
      -]
    • 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: -[
      -  "btc",
      -  "usdt",
      -  "usd1"
      -]
    • removedInput schema / properties / timezone / default
      Removed value: -"utc0"
    • 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"
      +]
  7. Changed12 schema fields changed
    • 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",
      +  "1m",
      +  "5m",
      +  "15m",
      +  "30m",
      +  "1h",
      +  "4h",
      +  "8h",
      +  "1d",
      +  "7d"
      +]
    • 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: +[
      +  "btc",
      +  "usdt",
      +  "usd1"
      +]
    • addedInput schema / properties / timezone / default
      Added value: +"utc0"
    • 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"
      +]
  8. Changed12 schema fields changed
    • 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",
      -  "1m",
      -  "5m",
      -  "15m",
      -  "30m",
      -  "1h",
      -  "4h",
      -  "8h",
      -  "1d",
      -  "7d"
      -]
    • 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: -[
      -  "btc",
      -  "usdt",
      -  "usd1"
      -]
    • removedInput schema / properties / timezone / default
      Removed value: -"utc0"
    • 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"
      +]
  9. Changed12 schema fields changed
    • 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",
      +  "1m",
      +  "5m",
      +  "15m",
      +  "30m",
      +  "1h",
      +  "4h",
      +  "8h",
      +  "1d",
      +  "7d"
      +]
    • 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: +[
      +  "btc",
      +  "usdt",
      +  "usd1"
      +]
    • addedInput schema / properties / timezone / default
      Added value: +"utc0"
    • 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"
      +]
  10. First observed

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, destructiveHint=false and openWorldHint, so the safety profile is fully covered elsewhere. The description adds nothing beyond that: no note on payload size, the limit-vs-from/to mutual exclusivity, default window behavior, or result ordering.

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 no filler. It is efficient, but the brevity comes at the cost of coverage rather than being a model of well-packed structure.

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 7-parameter market-data tool with no output schema, the description omits the returned shape (open/high/low/close/volume columns, ordering), the contract-name format that must pair with settle, and how limit interacts with from/to. Annotations carry safety but not the data-contract details an agent needs.

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 seven parameters (including the interval enum nuances and timezone) are already documented in the schema and the baseline applies. The description adds only the 'OHLCV' hint about the returned columns, nothing about contract or settle semantics.

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 pairs the verb 'Get' with a specific resource ('futures candlestick/OHLCV data') and the word 'futures' implicitly separates it from the spot, options and delivery candlestick siblings. It is clear what the tool returns, though it never names an alternative explicitly.

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 choose this over cex_spot_get_spot_candlesticks, cex_options_list_options_candlesticks or cex_dc_list_dc_candlesticks, and no prerequisite or rate-limit context. The agent must infer the choice purely from the word 'futures'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.