Skip to main content
Glama
IAcomunIA

CoinGecko MCP Server

by IAcomunIA

get_list_exchanges

Read-only

Retrieve a list of cryptocurrency exchanges with IDs and names from CoinGecko to identify trading platforms for market analysis or integration.

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 all the exchanges with ID and name

Response Schema

{
  $ref: '#/$defs/exchange_get_list_response',
  $defs: {
    exchange_get_list_response: {
      type: 'array',
      items: {
        type: 'object',
        properties: {
          id: {
            type: 'string',
            description: 'exchange ID'
          },
          name: {
            type: 'string',
            description: 'exchange name'
          }
        },
        required: [          'id',
          'name'
        ]
      }
    }
  }
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNofilter by status of exchanges, default: active
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 describing the response content (ID and name), which is useful beyond annotations. However, it doesn't cover other traits like rate limits, pagination, or error handling, leaving some gaps.

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?

The description is front-loaded with usage advice and purpose, but includes an output schema section that is redundant since there's no output schema in context signals, adding unnecessary length. The sentences are mostly efficient, but the inclusion of schema details reduces overall conciseness.

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 low complexity (2 parameters, no required params, no output schema), the description is mostly complete: it covers purpose, usage guidelines for parameters, and response content. However, it could improve by addressing sibling differentiation or more behavioral details, but it's adequate for this simple query tool.

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 the schema fully documents both parameters (status and jq_filter). The description adds value by strongly recommending jq_filter for performance and explaining its purpose, but doesn't provide additional semantic details beyond what's in the schema, such as default behaviors or usage examples for status.

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 states 'query all the exchanges with ID and name', which clearly indicates the verb (query) and resource (exchanges) with specific fields (ID and name). However, it doesn't explicitly differentiate from sibling tools like 'get_exchanges_tickers' or 'get_id_exchanges', which likely serve different purposes, so it misses full 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 clear context for 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'). However, it doesn't specify when to use this tool versus alternatives like other exchange-related siblings, so it lacks explicit 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