Skip to main content
Glama
ymylive
by ymylive

list_exchanges_directory

Retrieve a curated directory of centralized exchanges from CoinGecko, sorted by trust score and 24h BTC volume. Includes metadata like country, year established, trust score rank, and normalized volume.

Instructions

List centralized exchanges from CoinGecko's directory, ranked by trust score / volume.

This is CoinGecko's curated directory with metadata (year established, country, trust scores, 24h BTC-equivalent volume). For exchanges you can actually query in real time via this MCP, see list_supported_exchanges.

Args: per_page: 1..250 exchanges per page. page: Page number.

Returns: Array of exchanges with id, name, year_established, country, url, image, trust_score, trust_score_rank, trade_volume_24h_btc, trade_volume_24h_btc_normalized.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
per_pageNo
pageNo

Implementation Reference

  • The `list_exchanges_directory` MCP tool handler function. Decorated with @mcp.tool(), it calls `_cg_get('/exchanges', ...)` to fetch the CoinGecko exchanges directory with pagination (per_page capped at 1..250).
    @mcp.tool()
    async def list_exchanges_directory(per_page: int = 100, page: int = 1) -> Any:
        """List centralized exchanges from CoinGecko's directory, ranked by trust score / volume.
    
        This is CoinGecko's curated directory with metadata (year established,
        country, trust scores, 24h BTC-equivalent volume). For exchanges you can
        actually query in real time via this MCP, see `list_supported_exchanges`.
    
        Args:
            per_page: 1..250 exchanges per page.
            page: Page number.
    
        Returns:
            Array of exchanges with `id`, `name`, `year_established`, `country`,
            `url`, `image`, `trust_score`, `trust_score_rank`, `trade_volume_24h_btc`,
            `trade_volume_24h_btc_normalized`.
        """
        return await _cg_get(
            "/exchanges",
            {"per_page": max(1, min(per_page, 250)), "page": max(1, page)},
        )
  • The `mcp` instance is imported from `coin_mcp.core`, and the `@mcp.tool()` decorator on line 409 registers this function as an MCP tool.
    from .core import _bool_str, _cg_get, mcp
  • Input schema defined via type hints: `per_page: int = 100` (clamped 1-250) and `page: int = 1` (clamped >= 1). The return type is `Any` (JSON from CoinGecko).
    @mcp.tool()
    async def list_exchanges_directory(per_page: int = 100, page: int = 1) -> Any:
        """List centralized exchanges from CoinGecko's directory, ranked by trust score / volume.
    
        This is CoinGecko's curated directory with metadata (year established,
        country, trust scores, 24h BTC-equivalent volume). For exchanges you can
        actually query in real time via this MCP, see `list_supported_exchanges`.
    
        Args:
            per_page: 1..250 exchanges per page.
            page: Page number.
    
        Returns:
            Array of exchanges with `id`, `name`, `year_established`, `country`,
            `url`, `image`, `trust_score`, `trust_score_rank`, `trade_volume_24h_btc`,
            `trade_volume_24h_btc_normalized`.
        """
        return await _cg_get(
            "/exchanges",
            {"per_page": max(1, min(per_page, 250)), "page": max(1, page)},
        )
  • The `_cg_get` helper function used by the tool. It constructs the full CoinGecko API URL, adds auth headers, and delegates to the cached HTTP GET helper.
    async def _cg_get(path: str, params: dict[str, Any] | None = None) -> Any:
        return await _http_get(
            f"{_coingecko_base()}{path}",
            params=params,
            headers=_coingecko_headers(),
        )
  • The documentation/instructions table in `core.py` lists this tool as 'Browse all exchanges (CoinGecko directory) | list_exchanges_directory'.
    | Browse all exchanges (CoinGecko directory) | list_exchanges_directory |
Behavior4/5

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

No annotations provided, so description carries full burden. Clearly describes it as a read-only listing with specified return fields and sorting. Lacks explicit idempotency or safety statement, but the nature is obvious.

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?

Well-structured with purpose sentence, clarification, and Args/Returns sections. Each sentence adds value, though slightly longer than minimal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, description lists all return fields. Specifies sorting, distinguishes from sibling, and covers parameters. Complete for a list tool.

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 coverage 0% but description adds range for per_page (1..250) and clarifies page is a page number. Adds meaning beyond schema defaults and types.

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?

Explicitly states it lists centralized exchanges from CoinGecko's directory ranked by trust score/volume. Clearly distinguishes from sibling list_supported_exchanges, which is for live queryable exchanges.

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 tells when not to use (for live queryable exchanges) and provides alternative list_supported_exchanges. Also describes that it returns metadata for curated directory.

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/ymylive/coin-mcp'

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