Gate MCP

cex_fx_get_fx_funding_rate

Read-onlyIdempotent

Get funding rate history for a futures 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_funding_rate"
  }
}

Input Schema

Name	Required	Description
`to`	No	End timestamp in seconds
`from`	No	Start timestamp in seconds
`limit`	No	Maximum number of records to return
`settle`	Yes	Settlement currency
`contract`	Yes	Futures contract name

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

B3.2/5.0

Behavior3/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 fully covered. The description adds nothing beyond that — no note on result ordering, default time window, or pagination behavior with limit/from/to.

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 tight sentence with no wasted words and the resource front-loaded. Very short, but not padded.

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 hint at what a funding-rate record contains (rate value, timestamp interval) or at ordering. As written it is minimum viable for a history-retrieval tool whose params are fully schema-documented.

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 five parameters are documented in the schema itself, including the settle enum and timestamp units. The description adds no extra meaning such as default lookback window or how 'to' behaves when omitted.

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 ('Get') and resource ('funding rate history for a futures contract'), which is clearly distinct from candle/ticker/order-book siblings. It does not, however, distinguish itself from the close sibling cex_fx_list_batch_fx_funding_rates, leaving the agent to infer the difference.

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?

No guidance on when to use this versus the batch funding-rate sibling or any other fx tool. There is no mention of required conditions, time-range expectations, or 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.