Skip to main content
Glama

getExchangeMarkets

Read-onlyIdempotent

List the trading pairs (markets) on one exchange as a list, each with the pair, base and quote coin ids, latest price, 24h volume and category. Use for 'what pairs trade on Binance', 'markets on Kraken', 'BTC pairs on Coinbase'. For exchange-level stats such as trust score use getExchangeByID; find the exchangeId first with getExchanges. Read-only. Params: exchangeId (required) is an exchange id such as 'binance'; quotes (optional, default 'usd') is a comma-separated list of quote currencies for the figures, e.g. 'usd,btc'; limit (optional, default 50, max 250) caps how many markets return. No API key required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
quotesNo
rationaleYesREQUIRED. In 1-2 sentences explain WHY you are calling this tool and what you intend to do with the result. Examples: 'User asked for BTC price; calling getTickersById to fetch current USD value.' 'Building a portfolio dashboard; need OHLCV for ETH last 7 days.' This is logged and reviewed to improve the MCP. Do not include user PII or secrets; use generic descriptions.
exchangeIdYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
marketsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / rationale / description
      Previous value: -"REQUIRED. In 1-2 sentences explain WHY you are calling this tool and what you intend to do with the result. Examples: 'User asked for BTC price; calling getTickersById to fetch current USD value.' 'Building a portfolio dashboard; need OHLCV for ETH last 7 days.' This is logged and reviewed to improve the MCP. Do not include user PII or secrets — use generic descriptions."New value: +"REQUIRED. In 1-2 sentences explain WHY you are calling this tool and what you intend to do with the result. Examples: 'User asked for BTC price; calling getTickersById to fetch current USD value.' 'Building a portfolio dashboard; need OHLCV for ETH last 7 days.' This is logged and reviewed to improve the MCP. Do not include user PII or secrets; use generic descriptions."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": true,
      +  "properties": {
      +    "markets": {
      +      "items": {
      +        "additionalProperties": true,
      +        "properties": {
      +          "adjusted_volume_24h_share": {
      +            "type": "number"
      +          },
      +          "base_currency_id": {
      +            "type": "string"
      +          },
      +          "base_currency_name": {
      +            "type": "string"
      +          },
      +          "category": {
      +            "type": "string"
      +          },
      +          "fee_type": {
      +            "type": "string"
      +          },
      +          "last_updated": {
      +            "type": "string"
      +          },
      +          "market_url": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "outlier": {
      +            "type": "boolean"
      +          },
      +          "pair": {
      +            "type": "string"
      +          },
      +          "quote_currency_id": {
      +            "type": "string"
      +          },
      +          "quote_currency_name": {
      +            "type": "string"
      +          },
      +          "quotes": {
      +            "additionalProperties": {
      +              "additionalProperties": true,
      +              "properties": {
      +                "ath_date": {
      +                  "type": [
      +                    "string",
      +                    "null"
      +                  ]
      +                },
      +                "ath_price": {
      +                  "type": [
      +                    "number",
      +                    "null"
      +                  ]
      +                },
      +                "market_cap": {
      +                  "type": [
      +                    "number",
      +                    "null"
      +                  ]
      +                },
      +                "market_cap_change_24h": {
      +                  "type": [
      +                    "number",
      +                    "null"
      +                  ]
      +                },
      +                "percent_change_12h": {
      +                  "type": [
      +                    "number",
      +                    "null"
      +                  ]
      +                },
      +                "percent_change_15m": {
      +                  "type": [
      +                    "number",
      +                    "null"
      +                  ]
      +                },
      +                "percent_change_1h": {
      +                  "type": [
      +                    "number",
      +                    "null"
      +                  ]
      +                },
      +                "percent_change_1y": {
      +                  "type": [
      +                    "number",
      +                    "null"
      +                  ]
      +                },
      +                "percent_change_24h": {
      +                  "type": [
      +                    "number",
      +                    "null"
      +                  ]
      +                },
      +                "percent_change_30d": {
      +                  "type": [
      +                    "number",
      +                    "null"
      +                  ]
      +                },
      +                "percent_change_30m": {
      +                  "type": [
      +                    "number",
      +                    "null"
      +                  ]
      +                },
      +                "percent_change_6h": {
      +                  "type": [
      +                    "number",
      +                    "null"
      +                  ]
      +                },
      +                "percent_change_7d": {
      +                  "type": [
      +                    "number",
      +                    "null"
      +                  ]
      +                },
      +                "percent_from_price_ath": {
      +                  "type": [
      +                    "number",
      +                    "null"
      +                  ]
      +                },
      +                "price": {
      +                  "type": [
      +                    "number",
      +                    "null"
      +                  ]
      +                },
      +                "volume_24h": {
      +                  "type": [
      +                    "number",
      +                    "null"
      +                  ]
      +                },
      +                "volume_24h_change_24h": {
      +                  "type": [
      +                    "number",
      +                    "null"
      +                  ]
      +                }
      +              },
      +              "type": "object"
      +            },
      +            "type": "object"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "markets"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already carry readOnly/idempotent/non-destructive hints, so the description adds value with 'No API key required' and parameter default behaviors (quotes default 'usd', limit default 50). It also states output contents and examples. No contradictions with annotations.

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?

The description is dense but every sentence adds value: purpose, usage examples, sibling routing, auth/read-only status, and parameter details. Slight redundancy ('Read-only' repeats the annotation) but the overall structure is front-loaded and scannable.

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?

Covers purpose, output shape, parameter semantics, sibling routing, auth, and read-only behavior. An output schema exists to formalize return values. The only omission is the required rationale parameter, which is already described in the schema, so nothing critical is missing for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 25%, and the description compensates by explaining exchangeId with an example, quotes as a comma-separated list with default, and limit as a cap with bounds. It omits the required rationale parameter, but the schema's own property description covers it thoroughly.

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 opens with a specific verb and resource: 'List the trading pairs (markets) on one exchange as a list', and enumerates output fields. It also clarifies scope with usage examples ('what pairs trade on Binance') and distinguishes itself from the exchange-stats sibling by naming getExchangeByID.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Use for...' with concrete queries, names the alternative for other purposes ('For exchange-level stats... use getExchangeByID'), and instructs how to obtain the required ID ('find the exchangeId first with getExchanges'). No ambiguity about when to call this tool.

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.

Resources