Skip to main content
Glama

cex_alpha_list_alpha_currencies

Read-onlyIdempotent

List Alpha currencies.

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_alpha_list_alpha_currencies"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number
limitNoMaximum number of records returned in a single list
currencyNoAlpha currency ID, for example USDS02b5a8dd2f59a098, not the display symbol USDS. First call GET /alpha/currencies without currency, match the token by name, chain and address, and use the returned currency field. Paginate with page and limit. Use cex_alpha_list_alpha_currencies without currency to obtain the currency field.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • changedInput schema / properties / currency / description
      Previous value: -"Query by currency symbol"New value: +"Alpha currency ID, for example USDS02b5a8dd2f59a098, not the display symbol USDS. First call GET /alpha/currencies without currency, match the token by name, chain and address, and use the returned currency field. Paginate with page and limit. Use cex_alpha_list_alpha_currencies without currency to obtain the currency field."
    • addedInput schema / properties / limit / default
      Added value: +100
    • addedInput schema / properties / limit / format
      Added value: +"int32"
    • addedInput schema / properties / limit / maximum
      Added value: +100
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / page / default
      Added value: +1
    • addedInput schema / properties / page / format
      Added value: +"int32"
    • addedInput schema / properties / page / minimum
      Added value: +1
    • changedInput schema / properties / page / type
      Previous value: -"number"New value: +"integer"
  2. Changed9 schema fields changed
    • removedInput schema / properties / limit / default
      Removed value: -100
    • removedInput schema / properties / limit / format
      Removed value: -"int32"
    • removedInput schema / properties / limit / maximum
      Removed value: -100
    • removedInput schema / properties / limit / minimum
      Removed value: -1
    • changedInput schema / properties / limit / type
      Previous value: -"integer"New value: +"number"
    • removedInput schema / properties / page / default
      Removed value: -1
    • removedInput schema / properties / page / format
      Removed value: -"int32"
    • removedInput schema / properties / page / minimum
      Removed value: -1
    • changedInput schema / properties / page / type
      Previous value: -"integer"New value: +"number"
  3. Changed9 schema fields changed
    • addedInput schema / properties / limit / default
      Added value: +100
    • addedInput schema / properties / limit / format
      Added value: +"int32"
    • addedInput schema / properties / limit / maximum
      Added value: +100
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / page / default
      Added value: +1
    • addedInput schema / properties / page / format
      Added value: +"int32"
    • addedInput schema / properties / page / minimum
      Added value: +1
    • changedInput schema / properties / page / type
      Previous value: -"number"New value: +"integer"
  4. Changed9 schema fields changed
    • removedInput schema / properties / limit / default
      Removed value: -100
    • removedInput schema / properties / limit / format
      Removed value: -"int32"
    • removedInput schema / properties / limit / maximum
      Removed value: -100
    • removedInput schema / properties / limit / minimum
      Removed value: -1
    • changedInput schema / properties / limit / type
      Previous value: -"integer"New value: +"number"
    • removedInput schema / properties / page / default
      Removed value: -1
    • removedInput schema / properties / page / format
      Removed value: -"int32"
    • removedInput schema / properties / page / minimum
      Removed value: -1
    • changedInput schema / properties / page / type
      Previous value: -"integer"New value: +"number"
  5. Changed9 schema fields changed
    • addedInput schema / properties / limit / default
      Added value: +100
    • addedInput schema / properties / limit / format
      Added value: +"int32"
    • addedInput schema / properties / limit / maximum
      Added value: +100
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / page / default
      Added value: +1
    • addedInput schema / properties / page / format
      Added value: +"int32"
    • addedInput schema / properties / page / minimum
      Added value: +1
    • changedInput schema / properties / page / type
      Previous value: -"number"New value: +"integer"
  6. Changed9 schema fields changed
    • removedInput schema / properties / limit / default
      Removed value: -100
    • removedInput schema / properties / limit / format
      Removed value: -"int32"
    • removedInput schema / properties / limit / maximum
      Removed value: -100
    • removedInput schema / properties / limit / minimum
      Removed value: -1
    • changedInput schema / properties / limit / type
      Previous value: -"integer"New value: +"number"
    • removedInput schema / properties / page / default
      Removed value: -1
    • removedInput schema / properties / page / format
      Removed value: -"int32"
    • removedInput schema / properties / page / minimum
      Removed value: -1
    • changedInput schema / properties / page / type
      Previous value: -"integer"New value: +"number"
  7. Changed9 schema fields changed
    • addedInput schema / properties / limit / default
      Added value: +100
    • addedInput schema / properties / limit / format
      Added value: +"int32"
    • addedInput schema / properties / limit / maximum
      Added value: +100
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / page / default
      Added value: +1
    • addedInput schema / properties / page / format
      Added value: +"int32"
    • addedInput schema / properties / page / minimum
      Added value: +1
    • changedInput schema / properties / page / type
      Previous value: -"number"New value: +"integer"
  8. Changed9 schema fields changed
    • removedInput schema / properties / limit / default
      Removed value: -100
    • removedInput schema / properties / limit / format
      Removed value: -"int32"
    • removedInput schema / properties / limit / maximum
      Removed value: -100
    • removedInput schema / properties / limit / minimum
      Removed value: -1
    • changedInput schema / properties / limit / type
      Previous value: -"integer"New value: +"number"
    • removedInput schema / properties / page / default
      Removed value: -1
    • removedInput schema / properties / page / format
      Removed value: -"int32"
    • removedInput schema / properties / page / minimum
      Removed value: -1
    • changedInput schema / properties / page / type
      Previous value: -"integer"New value: +"number"
  9. Changed9 schema fields changed
    • addedInput schema / properties / limit / default
      Added value: +100
    • addedInput schema / properties / limit / format
      Added value: +"int32"
    • addedInput schema / properties / limit / maximum
      Added value: +100
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / page / default
      Added value: +1
    • addedInput schema / properties / page / format
      Added value: +"int32"
    • addedInput schema / properties / page / minimum
      Added value: +1
    • changedInput schema / properties / page / type
      Previous value: -"number"New value: +"integer"
  10. First observed

TDQS

C2.3/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 safety is covered. The description adds nothing beyond that — no note on pagination defaults (page/limit), result size limits, or what the returned records look like.

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?

A single four-word fragment with zero waste and no noise, but it is under-specified rather than aptly concise. It is front-loaded only in the trivial sense of being one sentence.

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?

With no output schema and a three-parameter list contract, the description should at minimum say what an alpha currency record is and how it differs from alpha tokens/tickers. Neither the domain term "Alpha" nor the sibling relationship is explained anywhere outside the schema.

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%, and the `currency` parameter's schema text is unusually detailed (ID format example, discovery workflow, pagination hint). The description itself contributes no parameter meaning, so the baseline 3 applies.

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

Purpose2/5

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

The description "List Alpha currencies" restates the tool name almost verbatim and never explains what "Alpha" is or what a "currency" record contains. It does not distinguish the tool from close siblings such as cex_alpha_list_alpha_tokens or cex_alpha_list_alpha_tickers, so an agent cannot tell which listing it needs.

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 the related alpha/token endpoints. The only routing information available (call without `currency` first to discover IDs) lives in the schema for the `currency` parameter, not in the description.

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.