Gate MCP

cex_dc_list_dc_insurance_ledger

Read-onlyIdempotent

List delivery insurance ledger.

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

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of records to return
`settle`	Yes	Settlement currency for delivery (e.g. usdt, btc)

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 2, 2026
- 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: +[
+  "usdt"
+]
```
- addedInput schema / required
```
Added value: +[
+  "settle"
+]
```
Changed6 schema fields changedOct 16, 2026
- 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: -[
-  "usdt"
-]
```
- removedInput schema / required
```
Removed value: -[
-  "settle"
-]
```
Changed6 schema fields changedOct 16, 2026
- 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: +[
+  "usdt"
+]
```
- addedInput schema / required
```
Added value: +[
+  "settle"
+]
```
Changed6 schema fields changedOct 16, 2026
- 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: -[
-  "usdt"
-]
```
- removedInput schema / required
```
Removed value: -[
-  "settle"
-]
```
Changed6 schema fields changedOct 16, 2026
- 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: +[
+  "usdt"
+]
```
- addedInput schema / required
```
Added value: +[
+  "settle"
+]
```
Changed6 schema fields changedOct 16, 2026
- 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: -[
-  "usdt"
-]
```
- removedInput schema / required
```
Removed value: -[
-  "settle"
-]
```
Changed6 schema fields changedOct 16, 2026
- 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: +[
+  "usdt"
+]
```
- addedInput schema / required
```
Added value: +[
+  "settle"
+]
```
Changed6 schema fields changedOct 16, 2026
- 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: -[
-  "usdt"
-]
```
- removedInput schema / required
```
Removed value: -[
-  "settle"
-]
```
Changed6 schema fields changedOct 16, 2026
- 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: +[
+  "usdt"
+]
```
- addedInput schema / required
```
Added value: +[
+  "settle"
+]
```
First observedApr 16, 2026

TDQS

C2.6/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 fully covered by structured data. The description adds nothing beyond that — no mention of pagination behavior, snapshot vs. streaming nature, or what a ledger entry represents.

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 short sentence with zero padding, front-loading the verb and resource. It is efficient, though bordering on under-specified rather than genuinely crisp.

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 two-parameter list tool with no output schema, the description leaves the agent without any sense of what records come back, whether results are paginated or time-bounded, or how this ledger differs from the fx/spot equivalents. Annotations cover safety but not semantics.

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%: 'settle' is documented with an enum and example, and 'limit' has default/min/max bounds. The description contributes no additional meaning, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a verb (List) and a resource (delivery insurance ledger), so the basic operation is identifiable. However, 'delivery insurance ledger' is domain jargon and the description does nothing to distinguish it from close siblings such as cex_fx_list_fx_insurance_ledger or cex_spot_get_spot_insurance_history.

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 the fx or spot insurance-ledger siblings, and no stated prerequisites or exclusions. The agent must infer everything from the 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.