Skip to main content
Glama
Sign In

Gate MCP

by io.github.gateio-dev
OverviewDiscussionsAdmin

cex_margin_get_uni_currency_pair

Read-onlyIdempotent

Get details of a specific unified margin 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_uni_currency_pair"
  }
}

Input Schema

NameRequiredDescriptionDefault
currency_pairYesCurrency pair, e.g. ADA_USDT

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / currency_pair / example
      Added value: +"AE_USDT"
  2. Changed1 schema field changed
    • removedInput schema / properties / currency_pair / example
      Removed value: -"AE_USDT"
  3. Changed1 schema field changed
    • addedInput schema / properties / currency_pair / example
      Added value: +"AE_USDT"
  4. Changed1 schema field changed
    • removedInput schema / properties / currency_pair / example
      Removed value: -"AE_USDT"
  5. Changed1 schema field changed
    • addedInput schema / properties / currency_pair / example
      Added value: +"AE_USDT"
  6. Changed1 schema field changed
    • removedInput schema / properties / currency_pair / example
      Removed value: -"AE_USDT"
  7. Changed1 schema field changed
    • addedInput schema / properties / currency_pair / example
      Added value: +"AE_USDT"
  8. Changed1 schema field changed
    • removedInput schema / properties / currency_pair / example
      Removed value: -"AE_USDT"
  9. Changed1 schema field changed
    • addedInput schema / properties / currency_pair / example
      Added value: +"AE_USDT"
  10. First observed

TDQS

A3.5/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 behavior, so the safety profile is covered. The description adds no details about authentication, rate limits, or response content, but it also does not contradict 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?

The description is a single front-loaded sentence with no filler or redundancy. It immediately states the operation and the target resource.

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 one-parameter read-only tool, the schema and annotations provide most of the necessary context. However, 'details' is vague and there is no output schema to clarify what fields are returned, leaving the response scope under-specified.

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?

There is one parameter, currency_pair, and schema description coverage is 100%, including an example. The description's phrase 'specific ... currency pair' adds no syntax, constraints, or format details beyond what the schema already provides.

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 ('Get'), resource ('details'), and domain ('unified margin currency pair'), making clear this retrieves one pair. It implicitly contrasts with the list sibling but does not name alternatives or explicitly distinguish from spot pair lookup.

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?

The word 'specific' implies use when one pair's details are needed, but there is no explicit when-to-use guidance, prerequisite, or named alternative such as cex_margin_list_uni_currency_pairs. The agent must infer the intended usage from the tool name and sibling list.

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