Skip to main content
Glama
Sign In

Gate MCP

by io.github.gateio-dev
OverviewDiscussionsAdmin

cex_options_get_options_settlement

Read-onlyIdempotent

Get a single options settlement record

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": {
      "contract": "<contract>",
      "underlying": "<underlying>",
      "at": "<at>"
    },
    "name": "cex_options_get_options_settlement"
  }
}

Input Schema

NameRequiredDescriptionDefault
atYesSettlement timestamp (Unix timestamp in seconds)
contractYesOptions contract name
underlyingYesUnderlying asset name, e.g. BTC_USDT

Schema Changelog

Changes observed during successful MCP inspections.

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

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 fully covered. The description adds nothing beyond that — no note on lookup-by-composite-key behavior, what happens when no settlement exists at the given timestamp, or data freshness.

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 zero waste. It is efficient, though the brevity reflects under-specification rather than disciplined compression of richer content.

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 three-required-parameter lookup with no output schema, the description should say at minimum that the parameters form a composite key identifying one settlement record, and what a settlement record contains. Neither is covered, leaving the agent to guess at return shape and empty-result behavior.

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 each of the three required parameters (at, contract, underlying) documented in the schema, so the baseline is 3. The description adds no meaning about how the three combine to uniquely identify a settlement record.

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) and resource (a single options settlement record), and the word 'single' implicitly contrasts with the sibling list_options_settlements. It never names that sibling or states the keying semantics, so differentiation is inferred rather than explicit.

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?

No guidance on when to use this versus cex_options_list_options_settlements or cex_options_get_options_contract. The agent must infer that this is the point-lookup counterpart to the list tool from the word 'single' alone.

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