Skip to main content
Glama
IAcomunIA

CoinGecko MCP Server

by IAcomunIA

get_id_exchanges

Read-only

Retrieve detailed cryptocurrency exchange information including name, establishment year, country, BTC volume, and top 100 tickers using the exchange's unique identifier.

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 data (name, year established, country, ...), exchange volume in BTC and top 100 tickers based on exchange's ID

Response Schema

{
  $ref: '#/$defs/exchange_get_id_response',
  $defs: {
    exchange_get_id_response: {
      type: 'object',
      properties: {
        alert_notice: {
          type: 'string',
          description: 'alert notice for exchange'
        },
        centralized: {
          type: 'boolean',
          description: 'exchange type (true for centralized, false for decentralized)'
        },
        coins: {
          type: 'number',
          description: 'number of coins listed on the exchange'
        },
        country: {
          type: 'string',
          description: 'exchange incorporated country'
        },
        description: {
          type: 'string',
          description: 'exchange description'
        },
        facebook_url: {
          type: 'string',
          description: 'exchange facebook url'
        },
        has_trading_incentive: {
          type: 'boolean',
          description: 'exchange trading incentive'
        },
        image: {
          type: 'string',
          description: 'exchange image url'
        },
        name: {
          type: 'string',
          description: 'exchange name'
        },
        other_url_1: {
          type: 'string'
        },
        other_url_2: {
          type: 'string'
        },
        pairs: {
          type: 'number',
          description: 'number of trading pairs on the exchange'
        },
        public_notice: {
          type: 'string',
          description: 'public notice for exchange'
        },
        reddit_url: {
          type: 'string',
          description: 'exchange reddit url'
        },
        slack_url: {
          type: 'string',
          description: 'exchange slack url'
        },
        telegram_url: {
          type: 'string',
          description: 'exchange telegram url'
        },
        tickers: {
          type: 'array',
          items: {
            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'
                    }
                  }
                }
              }
            }
          }
        },
        trade_volume_24h_btc: {
          type: 'number'
        },
        trust_score: {
          type: 'number',
          description: 'exchange trust score'
        },
        trust_score_rank: {
          type: 'number',
          description: 'exchange trust score rank'
        },
        twitter_handle: {
          type: 'string',
          description: 'exchange twitter handle'
        },
        url: {
          type: 'string',
          description: 'exchange website url'
        },
        year_established: {
          type: 'number',
          description: 'exchange established year'
        }
      }
    }
  }
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
dex_pair_formatNoset to `symbol` to display DEX pair base and target as symbols, default: `contract_address`
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?

The annotations already declare readOnlyHint=true, so the agent knows this is a safe read operation. The description adds useful behavioral context about performance optimization through jq_filter usage and mentions the response includes exchange data and tickers. However, it doesn't disclose other important traits like rate limits, authentication needs, or pagination behavior. With annotations covering the safety profile, a 3 is appropriate—the description adds some value but not comprehensive behavioral context.

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 appropriately sized with three sentences: performance advice, exception, and core purpose. It's front-loaded with the most actionable information (jq_filter usage). However, the inclusion of the full output schema within the description text adds unnecessary bulk that could be separated, slightly reducing efficiency.

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?

Given the tool's complexity (querying exchange data with tickers), the description is reasonably complete. It outlines the tool's purpose and provides performance guidance. The annotations cover read-only safety, and while there's no output schema in the structured data, the description includes a detailed response schema, compensating for that gap. However, it lacks information on error handling or example usage, preventing a perfect score.

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 67%, with two parameters well-documented in the schema (dex_pair_format and jq_filter). The description emphasizes the jq_filter parameter for performance but doesn't add semantic meaning beyond what the schema provides for any parameters. It doesn't explain the 'id' parameter's purpose or format. Given the moderate schema coverage, the description compensates minimally, warranting a baseline score of 3.

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?

The description clearly states the tool's purpose: 'query exchange's data (name, year established, country, ...), exchange volume in BTC and top 100 tickers based on exchange's ID'. It specifies the verb ('query'), resource ('exchange's data'), and scope ('based on exchange's ID'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'get_exchanges_tickers' or 'get_list_exchanges', which prevents a perfect score.

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 clear usage guidance with the strong recommendation to 'always use the `jq_filter` parameter to reduce the response size and improve performance', including an exception case ('Only omit if you're sure you don't need the data'). This gives practical advice for when to use the parameter. However, it doesn't specify when to use this tool versus alternatives among the many sibling tools, which limits the score.

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