Skip to main content
Glama
Nayshins

Cryptocurrency Market Data MCP Server

by Nayshins

list-exchanges

Retrieve a comprehensive list of cryptocurrency exchanges supported by the Cryptocurrency Market Data MCP Server for accessing real-time market data and trading information.

Instructions

List all supported cryptocurrency exchanges

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler logic for the 'list-exchanges' tool: checks the tool name and returns a formatted list of all supported exchanges from SUPPORTED_EXCHANGES.
    if name == "list-exchanges":
        exchange_list = "\n".join([f"- {ex.upper()}" for ex in SUPPORTED_EXCHANGES.keys()])
        return [
            types.TextContent(
                type="text",
                text=f"Supported exchanges:\n\n{exchange_list}"
            )
        ]
  • src/server.py:149-156 (registration)
    Registration of the 'list-exchanges' tool in the handle_list_tools function, including its name, description, and empty input schema.
    types.Tool(
        name="list-exchanges",
        description="List all supported cryptocurrency exchanges",
        inputSchema={
            "type": "object",
            "properties": {}
        },
    ),
  • Input schema for the 'list-exchanges' tool, which requires no parameters.
    inputSchema={
        "type": "object",
        "properties": {}
    },
  • Global dictionary defining all supported exchanges, directly used by the list-exchanges handler to generate the exchange list.
    SUPPORTED_EXCHANGES = {
        'binance': ccxt.binance,
        'coinbase': ccxt.coinbase,
        'kraken': ccxt.kraken,
        'kucoin': ccxt.kucoin,
        'hyperliquid': ccxt.hyperliquid,
        'huobi': ccxt.huobi,
        'bitfinex': ccxt.bitfinex,
        'bybit': ccxt.bybit,
        'okx': ccxt.okx,
        'mexc': ccxt.mexc
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('List') but doesn't describe traits like whether the list is static or dynamic, if it requires authentication, rate limits, or the format of the returned data. This leaves significant gaps for a tool with no structured safety hints.

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

Conciseness5/5

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

The description is a single, efficient sentence that directly states the tool's purpose without any waste. It's front-loaded and appropriately sized for a simple list operation, making it easy to parse quickly.

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 simplicity (0 parameters, no output schema), the description is adequate as a basic overview. However, with no annotations and siblings that might overlap, it lacks completeness in usage guidance and behavioral context, making it only minimally viable.

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?

The tool has 0 parameters, and schema description coverage is 100%, so there's no need for parameter details in the description. The description correctly avoids redundant information, earning a high score for not cluttering with unnecessary param semantics.

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 action ('List') and resource ('all supported cryptocurrency exchanges'), making the purpose immediately understandable. It doesn't differentiate from sibling tools like 'get-market-summary' or 'get-top-volumes', which might provide overlapping or related exchange data, so it doesn't reach 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 Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. For example, it doesn't specify if this is for a basic list, if siblings like 'get-market-summary' offer more detailed exchange info, or if it's the starting point for exchange selection. Without such context, usage is unclear.

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/Nayshins/mcp-server-ccxt'

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