Skip to main content
Glama

cex_options_list_options_trades

Read-onlyIdempotent

List public options trades

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cex_options_list_options_trades"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnd timestamp in seconds
fromNoStart timestamp in seconds
typeNoOption type: C for call, P for put
limitNoMaximum number of records to return
offsetNoList offset, starting from 0
contractNoOptions contract name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • addedInput schema / properties / from / format
      Added value: +"int64"
    • changedInput schema / properties / from / type
      Previous value: -"number"New value: +"integer"
    • 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 / offset / default
      Added value: +0
    • addedInput schema / properties / offset / minimum
      Added value: +0
    • changedInput schema / properties / offset / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / to / format
      Added value: +"int64"
    • changedInput schema / properties / to / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / type / format
      Added value: +"P"
  2. Changed12 schema fields changed
    • removedInput schema / properties / from / format
      Removed value: -"int64"
    • changedInput schema / properties / from / type
      Previous value: -"integer"New value: +"number"
    • 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 / offset / default
      Removed value: -0
    • removedInput schema / properties / offset / minimum
      Removed value: -0
    • changedInput schema / properties / offset / type
      Previous value: -"integer"New value: +"number"
    • removedInput schema / properties / to / format
      Removed value: -"int64"
    • changedInput schema / properties / to / type
      Previous value: -"integer"New value: +"number"
    • removedInput schema / properties / type / format
      Removed value: -"P"
  3. Changed12 schema fields changed
    • addedInput schema / properties / from / format
      Added value: +"int64"
    • changedInput schema / properties / from / type
      Previous value: -"number"New value: +"integer"
    • 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 / offset / default
      Added value: +0
    • addedInput schema / properties / offset / minimum
      Added value: +0
    • changedInput schema / properties / offset / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / to / format
      Added value: +"int64"
    • changedInput schema / properties / to / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / type / format
      Added value: +"P"
  4. Changed12 schema fields changed
    • removedInput schema / properties / from / format
      Removed value: -"int64"
    • changedInput schema / properties / from / type
      Previous value: -"integer"New value: +"number"
    • 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 / offset / default
      Removed value: -0
    • removedInput schema / properties / offset / minimum
      Removed value: -0
    • changedInput schema / properties / offset / type
      Previous value: -"integer"New value: +"number"
    • removedInput schema / properties / to / format
      Removed value: -"int64"
    • changedInput schema / properties / to / type
      Previous value: -"integer"New value: +"number"
    • removedInput schema / properties / type / format
      Removed value: -"P"
  5. Changed12 schema fields changed
    • addedInput schema / properties / from / format
      Added value: +"int64"
    • changedInput schema / properties / from / type
      Previous value: -"number"New value: +"integer"
    • 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 / offset / default
      Added value: +0
    • addedInput schema / properties / offset / minimum
      Added value: +0
    • changedInput schema / properties / offset / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / to / format
      Added value: +"int64"
    • changedInput schema / properties / to / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / type / format
      Added value: +"P"
  6. Changed12 schema fields changed
    • removedInput schema / properties / from / format
      Removed value: -"int64"
    • changedInput schema / properties / from / type
      Previous value: -"integer"New value: +"number"
    • 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 / offset / default
      Removed value: -0
    • removedInput schema / properties / offset / minimum
      Removed value: -0
    • changedInput schema / properties / offset / type
      Previous value: -"integer"New value: +"number"
    • removedInput schema / properties / to / format
      Removed value: -"int64"
    • changedInput schema / properties / to / type
      Previous value: -"integer"New value: +"number"
    • removedInput schema / properties / type / format
      Removed value: -"P"
  7. Changed12 schema fields changed
    • addedInput schema / properties / from / format
      Added value: +"int64"
    • changedInput schema / properties / from / type
      Previous value: -"number"New value: +"integer"
    • 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 / offset / default
      Added value: +0
    • addedInput schema / properties / offset / minimum
      Added value: +0
    • changedInput schema / properties / offset / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / to / format
      Added value: +"int64"
    • changedInput schema / properties / to / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / type / format
      Added value: +"P"
  8. Changed12 schema fields changed
    • removedInput schema / properties / from / format
      Removed value: -"int64"
    • changedInput schema / properties / from / type
      Previous value: -"integer"New value: +"number"
    • 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 / offset / default
      Removed value: -0
    • removedInput schema / properties / offset / minimum
      Removed value: -0
    • changedInput schema / properties / offset / type
      Previous value: -"integer"New value: +"number"
    • removedInput schema / properties / to / format
      Removed value: -"int64"
    • changedInput schema / properties / to / type
      Previous value: -"integer"New value: +"number"
    • removedInput schema / properties / type / format
      Removed value: -"P"
  9. Changed12 schema fields changed
    • addedInput schema / properties / from / format
      Added value: +"int64"
    • changedInput schema / properties / from / type
      Previous value: -"number"New value: +"integer"
    • 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 / offset / default
      Added value: +0
    • addedInput schema / properties / offset / minimum
      Added value: +0
    • changedInput schema / properties / offset / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / to / format
      Added value: +"int64"
    • changedInput schema / properties / to / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / type / format
      Added value: +"P"
  10. First observed

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The word 'public' implies no authentication, which is a small addition, but the description says nothing about pagination semantics, result size, ordering, or whether the 'from'/'to' window is bounded—context an agent needs for a timestamp-ranged listing.

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

Conciseness3/5

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

Five words, front-loaded and free of filler, so nothing is wasteful. However, the brevity edges into under-specification rather than disciplined conciseness—a single extra clause on filtering or pagination would cost little and add real value.

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?

Six optional parameters, no output schema, and no annotations beyond safety flags; the description does not explain what a trade record contains, how pagination with limit/offset should be driven, or how the contract/type filters combine. Material gaps remain for an agent invoking a ranged, paginated market-data listing.

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 all six parameters (to, from, type, limit, offset, contract) are already documented in the schema with formats, defaults and bounds. The description adds no additional meaning such as filter interaction or default time-window behavior, so baseline 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 ('List ... options trades') and the qualifier 'public' distinguishes it from any private/user-scoped trade endpoints. It does not explicitly differentiate from sibling trade-listing tools such as cex_fx_get_fx_trades or cex_spot_get_spot_trades, though the options namespace in the name makes the market scope inferable.

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 when-to-use guidance, no prerequisites, and no mention of alternatives (e.g. order book or candlesticks siblings for other views of the options market). The agent must infer the use case entirely from the name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.