Gate MCP

cex_mcl_get_multi_collateral_current_rate

Read-onlyIdempotent

Get current interest rates for specified currencies in multi-collateral loans (public)

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": {
      "currencies": "<currencies>"
    },
    "name": "cex_mcl_get_multi_collateral_current_rate"
  }
}

Input Schema

Name	Required	Description	Default
`vip_level`	No	VIP level, defaults to 0 if not specified	0
`currencies`	Yes	Currency names separated by commas, e.g. BTC,ETH,USDT. Maximum 100 items

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 2, 2026
- addedInput schema / properties / currencies / items
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / currencies / maxItems
```
Added value: +100
```
- addedInput schema / properties / currencies / minItems
```
Added value: +1
```
- addedInput schema / properties / vip_level / default
```
Added value: +"0"
```
Changed4 schema fields changedOct 16, 2026
- removedInput schema / properties / currencies / items
```
Removed value: -{
-  "type": "string"
-}
```
- removedInput schema / properties / currencies / maxItems
```
Removed value: -100
```
- removedInput schema / properties / currencies / minItems
```
Removed value: -1
```
- removedInput schema / properties / vip_level / default
```
Removed value: -"0"
```
Changed4 schema fields changedOct 16, 2026
- addedInput schema / properties / currencies / items
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / currencies / maxItems
```
Added value: +100
```
- addedInput schema / properties / currencies / minItems
```
Added value: +1
```
- addedInput schema / properties / vip_level / default
```
Added value: +"0"
```
Changed4 schema fields changedOct 16, 2026
- removedInput schema / properties / currencies / items
```
Removed value: -{
-  "type": "string"
-}
```
- removedInput schema / properties / currencies / maxItems
```
Removed value: -100
```
- removedInput schema / properties / currencies / minItems
```
Removed value: -1
```
- removedInput schema / properties / vip_level / default
```
Removed value: -"0"
```
Changed4 schema fields changedOct 16, 2026
- addedInput schema / properties / currencies / items
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / currencies / maxItems
```
Added value: +100
```
- addedInput schema / properties / currencies / minItems
```
Added value: +1
```
- addedInput schema / properties / vip_level / default
```
Added value: +"0"
```
Changed4 schema fields changedOct 16, 2026
- removedInput schema / properties / currencies / items
```
Removed value: -{
-  "type": "string"
-}
```
- removedInput schema / properties / currencies / maxItems
```
Removed value: -100
```
- removedInput schema / properties / currencies / minItems
```
Removed value: -1
```
- removedInput schema / properties / vip_level / default
```
Removed value: -"0"
```
Changed4 schema fields changedOct 16, 2026
- addedInput schema / properties / currencies / items
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / currencies / maxItems
```
Added value: +100
```
- addedInput schema / properties / currencies / minItems
```
Added value: +1
```
- addedInput schema / properties / vip_level / default
```
Added value: +"0"
```
Changed4 schema fields changedOct 16, 2026
- removedInput schema / properties / currencies / items
```
Removed value: -{
-  "type": "string"
-}
```
- removedInput schema / properties / currencies / maxItems
```
Removed value: -100
```
- removedInput schema / properties / currencies / minItems
```
Removed value: -1
```
- removedInput schema / properties / vip_level / default
```
Removed value: -"0"
```
Changed4 schema fields changedOct 16, 2026
- addedInput schema / properties / currencies / items
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / currencies / maxItems
```
Added value: +100
```
- addedInput schema / properties / currencies / minItems
```
Added value: +1
```
- addedInput schema / properties / vip_level / default
```
Added value: +"0"
```
First observedApr 16, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description's only extra signal is '(public)', which usefully implies no authentication is required, but nothing is said about rate limits, pagination, or how fresh the 'current' rate is.

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 front-loaded sentence with no filler. It is tightly sized, though the parenthetical '(public)' is the only detail carrying extra weight.

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 two-parameter read tool with full annotation and schema coverage, the description is adequate but thin: with no output schema, an agent gets no hint about the shape of the returned rates or what vip_level does to them.

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 parameters (vip_level, currencies) are already documented in the schema. The phrase 'for specified currencies' restates the schema without adding format or batching semantics, so the baseline of 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 and resource: 'Get current interest rates' for currencies in multi-collateral loans. The word 'current' implicitly separates it from the sibling cex_mcl_get_multi_collateral_fix_rate, but no sibling is named explicitly.

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?

Usage is only implied: an agent can infer this is the live-rate lookup versus the fixed-rate sibling, but the description never states when to prefer one over the other or any prerequisites beyond '(public)'.

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.