Skip to main content
Glama
Sign In

Gate MCP

by io.github.gateio-dev
OverviewDiscussionsAdmin

cex_fx_get_fx_tickers

Read-onlyIdempotent

Get ticker information for futures contracts

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": {
      "settle": "<settle>"
    },
    "name": "cex_fx_get_fx_tickers"
  }
}

Input Schema

NameRequiredDescriptionDefault
settleYesSettlement currency
contractNoFutures contract name. Only returns data for this contract if specified

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / settle / enum
      Added value: +[
+  "btc",
+  "usdt",
+  "usd1"
+]
    • addedInput schema / required
      Added value: +[
+  "settle"
+]
  2. Changed2 schema fields changed
    • removedInput schema / properties / settle / enum
      Removed value: -[
-  "btc",
-  "usdt",
-  "usd1"
-]
    • removedInput schema / required
      Removed value: -[
-  "settle"
-]
  3. Changed2 schema fields changed
    • addedInput schema / properties / settle / enum
      Added value: +[
+  "btc",
+  "usdt",
+  "usd1"
+]
    • addedInput schema / required
      Added value: +[
+  "settle"
+]
  4. Changed2 schema fields changed
    • removedInput schema / properties / settle / enum
      Removed value: -[
-  "btc",
-  "usdt",
-  "usd1"
-]
    • removedInput schema / required
      Removed value: -[
-  "settle"
-]
  5. Changed2 schema fields changed
    • addedInput schema / properties / settle / enum
      Added value: +[
+  "btc",
+  "usdt",
+  "usd1"
+]
    • addedInput schema / required
      Added value: +[
+  "settle"
+]
  6. Changed2 schema fields changed
    • removedInput schema / properties / settle / enum
      Removed value: -[
-  "btc",
-  "usdt",
-  "usd1"
-]
    • removedInput schema / required
      Removed value: -[
-  "settle"
-]
  7. Changed2 schema fields changed
    • addedInput schema / properties / settle / enum
      Added value: +[
+  "btc",
+  "usdt",
+  "usd1"
+]
    • addedInput schema / required
      Added value: +[
+  "settle"
+]
  8. Changed2 schema fields changed
    • removedInput schema / properties / settle / enum
      Removed value: -[
-  "btc",
-  "usdt",
-  "usd1"
-]
    • removedInput schema / required
      Removed value: -[
-  "settle"
-]
  9. Changed2 schema fields changed
    • addedInput schema / properties / settle / enum
      Added value: +[
+  "btc",
+  "usdt",
+  "usd1"
+]
    • addedInput schema / required
      Added value: +[
+  "settle"
+]
  10. First observed

TDQS

C2.9/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false. The description adds no behavioral context beyond the annotations, such as what ticker fields are returned, whether settlement currency affects coverage, or any rate or freshness behavior.

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?

The description is a single front-loaded sentence with no wasted words. It is efficient but perhaps too terse for a tool with settlement and contract filtering, even though terseness is mainly a completeness issue.

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?

With no output schema, the description should explain more about the returned ticker data and how the settlement and contract filters affect results. It also fails to situate the tool among the many sibling ticker and contract endpoints, leaving the agent to infer usage.

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 both the required settlement enum and the optional contract filter are fully documented in the schema. The description adds no parameter meaning beyond that, which is acceptable given complete schema coverage.

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 uses a clear verb ('Get') and resource ('ticker information') scoped to futures contracts. It is distinguishable from spot or options ticker tools, but it does not distinguish itself from nearby FX siblings such as cex_fx_list_contract_stats or cex_fx_get_fx_contract.

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 explicit guidance on when to use this tool versus the many sibling ticker and contract tools. The only implied usage is the bare purpose statement, with no prerequisites, exclusions, or alternatives named.

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

All Gate MCP toolsInspect
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.

Resources