Skip to main content
Glama
IAcomunIA

CoinGecko MCP Server

by IAcomunIA

get_exchanges_tickers

Read-only

Retrieve cryptocurrency trading data from specific exchanges, including prices, volumes, and market metrics for informed trading decisions.

Instructions

When using this tool, always use the jq_filter parameter to reduce the response size and improve performance.

Only omit if you're sure you don't need the data.

This endpoint allows you to query exchange's tickers based on exchange's ID

Response Schema

{
  $ref: '#/$defs/ticker_get_response',
  $defs: {
    ticker_get_response: {
      type: 'object',
      properties: {
        name: {
          type: 'string',
          description: 'coin name'
        },
        tickers: {
          type: 'array',
          description: 'list of tickers',
          items: {
            type: 'object',
            properties: {
              base: {
                type: 'string',
                description: 'coin ticker base currency'
              },
              bid_ask_spread_percentage: {
                type: 'number',
                description: 'coin ticker bid ask spread percentage'
              },
              coin_id: {
                type: 'string',
                description: 'coin ticker base currency coin ID'
              },
              converted_last: {
                type: 'object',
                description: 'coin ticker converted last price',
                properties: {
                  btc: {
                    type: 'number'
                  },
                  eth: {
                    type: 'number'
                  },
                  usd: {
                    type: 'number'
                  }
                }
              },
              converted_volume: {
                type: 'object',
                description: 'coin ticker converted volume',
                properties: {
                  btc: {
                    type: 'number'
                  },
                  eth: {
                    type: 'number'
                  },
                  usd: {
                    type: 'number'
                  }
                }
              },
              cost_to_move_down_usd: {
                type: 'number',
                description: 'coin ticker cost to move down in usd'
              },
              cost_to_move_up_usd: {
                type: 'number',
                description: 'coin ticker cost to move up in usd'
              },
              is_anomaly: {
                type: 'boolean',
                description: 'coin ticker anomaly'
              },
              is_stale: {
                type: 'boolean',
                description: 'coin ticker stale'
              },
              last: {
                type: 'number',
                description: 'coin ticker last price'
              },
              last_fetch_at: {
                type: 'string',
                description: 'coin ticker last fetch timestamp'
              },
              last_traded_at: {
                type: 'string',
                description: 'coin ticker last traded timestamp'
              },
              market: {
                type: 'object',
                description: 'coin ticker exchange',
                properties: {
                  has_trading_incentive: {
                    type: 'boolean',
                    description: 'exchange trading incentive'
                  },
                  identifier: {
                    type: 'string',
                    description: 'exchange identifier'
                  },
                  name: {
                    type: 'string',
                    description: 'exchange name'
                  },
                  logo: {
                    type: 'string',
                    description: 'exchange image url'
                  }
                },
                required: [                  'has_trading_incentive',
                  'identifier',
                  'name'
                ]
              },
              target: {
                type: 'string',
                description: 'coin ticker target currency'
              },
              target_coin_id: {
                type: 'string',
                description: 'coin ticker target currency coin ID'
              },
              timestamp: {
                type: 'string',
                description: 'coin ticker timestamp'
              },
              token_info_url: {
                type: 'string',
                description: 'coin ticker token info url'
              },
              trade_url: {
                type: 'string',
                description: 'coin ticker trade url'
              },
              trust_score: {
                type: 'string',
                description: 'coin ticker trust score'
              },
              volume: {
                type: 'number',
                description: 'coin ticker volume'
              }
            }
          }
        }
      }
    }
  }
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
coin_idsNofilter tickers by coin IDs, comma-separated if querying more than 1 coin *refers to [`/coins/list`](/reference/coins-list).
depthNoinclude 2% orderbook depth (Example: cost_to_move_up_usd & cost_to_move_down_usd),default: false
dex_pair_formatNoset to `symbol` to display DEX pair base and target as symbols, default: `contract_address`
include_exchange_logoNoinclude exchange logo, default: false
orderNouse this to sort the order of responses, default: trust_score_desc
pageNopage through results
jq_filterNoA jq filter to apply to the response to include certain fields. Consult the output schema in the tool description to see the fields that are available. For example: to include only the `name` field in every object of a results array, you can provide ".results[].name". For more information, see the [jq documentation](https://jqlang.org/manual/).
Behavior3/5

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

Annotations provide readOnlyHint=true, indicating a safe read operation. The description adds behavioral context by emphasizing performance optimization with 'jq_filter' and mentioning the response schema, which helps the agent understand output structure. However, it doesn't disclose other traits like rate limits, authentication needs, or pagination behavior (implied by 'page' parameter), leaving gaps despite annotations.

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

Conciseness2/5

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

The description is poorly structured: it starts with usage advice for 'jq_filter', then states the purpose, and includes a large, embedded JSON output schema that makes it verbose and hard to parse. The output schema should be in a separate field, not in the description. Sentences are useful but not front-loaded efficiently, reducing clarity.

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?

Given the tool's complexity (8 parameters, high schema coverage, readOnlyHint annotation, no output schema), the description is partially complete. It covers purpose and 'jq_filter' guidance but lacks details on error handling, rate limits, or full behavioral context. The embedded output schema compensates for no output schema field, but this is structurally inappropriate, leaving gaps in completeness.

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 high (88%), so the schema already documents most parameters well. The description adds value by strongly recommending 'jq_filter' for performance and referencing the output schema for field availability, but it doesn't provide additional semantic details beyond what the schema offers, such as examples for 'id' or 'coin_ids'. Baseline 3 is appropriate given the schema's coverage.

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

Purpose3/5

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

The description states 'query exchange's tickers based on exchange's ID', which provides a verb ('query') and resource ('exchange's tickers'), but it's vague about what tickers are (e.g., cryptocurrency trading pairs) and doesn't differentiate from siblings like 'get_id_exchanges' or 'get_list_exchanges'. The purpose is clear but lacks specificity and sibling distinction.

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

Usage Guidelines4/5

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

The description provides explicit guidance on when to use the 'jq_filter' parameter ('always use... to reduce response size and improve performance') and when to omit it ('Only omit if you're sure you don't need the data'), which is clear context for usage. However, it doesn't mention when to use this tool versus alternatives like 'get_coins_markets' or other sibling tools, so it lacks full alternative guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/IAcomunIA/MCP_firts'

If you have feedback or need assistance with the MCP directory API, please join our Discord server