Gate MCP

cex_dc_list_dc_tickers

Read-onlyIdempotent

List delivery tickers.

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

Input Schema

Name	Required	Description	Default
`settle`	Yes	Settlement currency for delivery (e.g. usdt, btc)
`contract`	No	Optional delivery contract identifier; if set, only that contract's ticker is returned

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 2, 2026
- addedInput schema / properties / settle / enum
```
Added value: +[
+  "usdt"
+]
```
- addedInput schema / required
```
Added value: +[
+  "settle"
+]
```
Changed2 schema fields changedOct 16, 2026
- removedInput schema / properties / settle / enum
```
Removed value: -[
-  "usdt"
-]
```
- removedInput schema / required
```
Removed value: -[
-  "settle"
-]
```
Changed2 schema fields changedOct 16, 2026
- addedInput schema / properties / settle / enum
```
Added value: +[
+  "usdt"
+]
```
- addedInput schema / required
```
Added value: +[
+  "settle"
+]
```
Changed2 schema fields changedOct 16, 2026
- removedInput schema / properties / settle / enum
```
Removed value: -[
-  "usdt"
-]
```
- removedInput schema / required
```
Removed value: -[
-  "settle"
-]
```
Changed2 schema fields changedOct 16, 2026
- addedInput schema / properties / settle / enum
```
Added value: +[
+  "usdt"
+]
```
- addedInput schema / required
```
Added value: +[
+  "settle"
+]
```
Changed2 schema fields changedOct 16, 2026
- removedInput schema / properties / settle / enum
```
Removed value: -[
-  "usdt"
-]
```
- removedInput schema / required
```
Removed value: -[
-  "settle"
-]
```
Changed2 schema fields changedOct 16, 2026
- addedInput schema / properties / settle / enum
```
Added value: +[
+  "usdt"
+]
```
- addedInput schema / required
```
Added value: +[
+  "settle"
+]
```
Changed2 schema fields changedOct 16, 2026
- removedInput schema / properties / settle / enum
```
Removed value: -[
-  "usdt"
-]
```
- removedInput schema / required
```
Removed value: -[
-  "settle"
-]
```
Changed2 schema fields changedOct 16, 2026
- addedInput schema / properties / settle / enum
```
Added value: +[
+  "usdt"
+]
```
- addedInput schema / required
```
Added value: +[
+  "settle"
+]
```
First observedApr 16, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context beyond the basic purpose, such as scope, pagination, rate limits, or what the returned tickers include.

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 filler or repetition. It is concise, though its terseness means it carries very little explanatory structure.

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?

For a simple list endpoint with fully described parameters and read-only annotations, the description is minimally adequate. However, it lacks usage guidance and does not clarify what a delivery ticker represents or how results are scoped, leaving some gaps for an agent selecting among many DC sibling tools.

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%, with clear descriptions for both the required settle enum and optional contract filter. The description does not add parameter semantics, but baseline 3 is appropriate because the schema fully documents the inputs.

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 states a specific verb+resource: "List delivery tickers." This clearly identifies a read/list operation over delivery tickers rather than contracts, candlesticks, trades, or other sibling resources, though it does not explicitly name or differentiate against those siblings.

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 tool versus alternatives such as cex_dc_list_dc_contracts or cex_dc_get_dc_contract. The intended usage is only implied by the word "List" and the resource name.

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.