Gate MCP

cex_fx_get_fx_premium_index

Read-onlyIdempotent

Get premium index (mark price minus index price) history for a contract

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

Input Schema

Name	Required	Description	Default
`to`	No	End timestamp in seconds, defaults to current time if not specified
`from`	No	Start timestamp in seconds. Defaults to to - 100 * interval if not specified
`limit`	No	Maximum number of data points to return. Mutually exclusive with from/to parameters
`settle`	Yes	Settlement currency
`contract`	Yes	Futures contract name
`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: +[
+  "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 / 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: -[
-  "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 / 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: +[
+  "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 / 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: -[
-  "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 / 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: +[
+  "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 / 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: -[
-  "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 / 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: +[
+  "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 / 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: -[
-  "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 / 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: +[
+  "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 / 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

A3.5/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds the definition of the returned metric, which is genuine value, but says nothing about pagination limits, default time window behavior, or ordering of returned points.

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

Conciseness5/5

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

One front-loaded sentence with zero filler; the metric definition sits in parentheses exactly where it is needed.

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 six parameters, defaults on interval/limit/from/to, and no output schema, the definition is adequate but thin: it never explains that omitting from/to yields a default window, nor what settle values mean for contract selection. An agent can call it, but only by leaning entirely on the schema.

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 includes enum values, defaults, and the note that limit is mutually exclusive with from/to. The description adds no parameter-level meaning beyond the schema, so the baseline 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?

States a specific verb+resource ('Get premium index history') and parenthetically defines the metric as mark price minus index price for a contract, which distinguishes it from neighbors like cex_fx_get_fx_funding_rate or cex_fx_get_fx_candlesticks. It stops short of explicitly naming a sibling it should be preferred over, so not a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The word 'history' implies a time-series query, and the required contract/settle params make the context inferable, but there is no explicit when-to-use guidance, no mention of the from/to vs limit tradeoff, and no exclusion of alternatives.

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.