Skip to main content
Glama
Sign In

Gate MCP

by io.github.gateio-dev
OverviewDiscussionsAdmin

cex_margin_get_market_margin_tier

Read-onlyIdempotent

Get margin leverage tiers for a currency pair

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": {
      "currency_pair": "<currency_pair>"
    },
    "name": "cex_margin_get_market_margin_tier"
  }
}

Input Schema

NameRequiredDescriptionDefault
currency_pairYesCurrency pair, e.g. BTC_USDT

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, which cover the safety profile. The description adds no behavioral detail beyond the word 'Get', so it neither enhances nor contradicts the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, well-formed sentence with no filler or redundant information. Every word contributes to stating the tool's function.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple, read-only, one-parameter tool with rich annotations, the description is nearly sufficient. It does not explain the return format or the exact meaning of 'margin leverage tiers', but the absence of an output schema and the simplicity of the operation keep the gap small. A 4 is appropriate.

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?

The schema provides 100% coverage for the single parameter, including an example (BTC_USDT). The description's phrase 'for a currency pair' only restates the schema field, adding no additional semantic value beyond what is already documented.

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

Purpose5/5

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

The description 'Get margin leverage tiers for a currency pair' clearly identifies the action (get), the resource (margin leverage tiers), and the scope (currency pair). It is specific and distinguishable from sibling tools like cex_margin_get_uni_currency_pair or spot/list tools.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention related tools, when not to use it, or any distinguishing context beyond the basic purpose.

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