Skip to main content
Glama
Nayshins

Cryptocurrency Market Data MCP Server

by Nayshins

get-market-summary

Retrieve detailed market summary data for cryptocurrency trading pairs from major exchanges to analyze current market conditions and trading information.

Instructions

Get detailed market summary for a cryptocurrency pair from a specific exchange

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesTrading pair symbol (e.g., BTC/USDT, ETH/USDT)
exchangeNoExchange to use (supported: binance, coinbase, kraken, kucoin, hyperliquid, huobi, bitfinex, bybit, okx, mexc)binance

Implementation Reference

  • The handler executes the 'get-market-summary' tool by fetching the ticker data from the specified exchange using ccxt and formatting it with the format_ticker helper.
    elif name == "get-market-summary":
        symbol = arguments.get("symbol", "").upper()
        ticker = await exchange.fetch_ticker(symbol)
    
        formatted_data = await format_ticker(ticker, exchange_id)
        return [
            types.TextContent(
                type="text",
                text=f"Market summary for {symbol}:\n\n{formatted_data}"
            )
        ]
  • src/server.py:120-134 (registration)
    The tool registration in list_tools(), including name, description, and input schema.
    types.Tool(
        name="get-market-summary",
        description="Get detailed market summary for a cryptocurrency pair from a specific exchange",
        inputSchema={
            "type": "object",
            "properties": {
                "symbol": {
                    "type": "string",
                    "description": "Trading pair symbol (e.g., BTC/USDT, ETH/USDT)",
                },
                "exchange": get_exchange_schema()
            },
            "required": ["symbol"],
        },
    ),
  • Schema definition for the exchange parameter, referenced in the tool's inputSchema.
    def get_exchange_schema() -> Dict[str, Any]:
        """Get the JSON schema for exchange selection."""
        return {
            "type": "string",
            "description": f"Exchange to use (supported: {', '.join(SUPPORTED_EXCHANGES.keys())})",
            "enum": list(SUPPORTED_EXCHANGES.keys()),
            "default": "binance"
        }
  • Helper function to format the ticker data into a human-readable market summary string.
    async def format_ticker(ticker: Dict[str, Any], exchange_id: str) -> str:
        """Format ticker data into a readable string."""
        return (
            f"Exchange: {exchange_id.upper()}\n"
            f"Symbol: {ticker.get('symbol')}\n"
            f"Last Price: {ticker.get('last', 'N/A')}\n"
            f"24h High: {ticker.get('high', 'N/A')}\n"
            f"24h Low: {ticker.get('low', 'N/A')}\n"
            f"24h Volume: {ticker.get('baseVolume', 'N/A')}\n"
            f"Bid: {ticker.get('bid', 'N/A')}\n"
            f"Ask: {ticker.get('ask', 'N/A')}\n"
            "---"
        )
  • Helper to retrieve or initialize the ccxt exchange instance, used in the handler.
    async def get_exchange(exchange_id: str) -> ccxt.Exchange:
        """Get or create an exchange instance."""
        exchange_id = exchange_id.lower()
        if exchange_id not in SUPPORTED_EXCHANGES:
            raise ValueError(f"Unsupported exchange: {exchange_id}")
    
        if exchange_id not in exchange_instances:
            exchange_class = SUPPORTED_EXCHANGES[exchange_id]
            exchange_instances[exchange_id] = exchange_class()
    
        return exchange_instances[exchange_id]
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states what the tool does but fails to describe key traits like whether it's a read-only operation, potential rate limits, authentication needs, error handling, or the format of the returned summary. This leaves significant gaps in understanding how the tool behaves beyond its basic function.

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 unnecessary words or fluff. It is front-loaded and appropriately sized for its function, making it easy to understand quickly.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It specifies the tool's function but omits critical details such as the structure of the returned market summary, potential side effects, or error conditions. For a tool with no structured behavioral data, this leaves too many unknowns for effective agent use.

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?

The input schema has 100% description coverage, clearly documenting both parameters with examples and an enum for 'exchange'. The description adds no additional meaning beyond this, as it doesn't elaborate on parameter usage or constraints. With high schema coverage, the baseline score of 3 is appropriate, as the schema adequately handles parameter semantics without extra description.

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 ('Get detailed market summary') and resource ('for a cryptocurrency pair from a specific exchange'), making the purpose unambiguous. However, it doesn't explicitly differentiate this tool from its siblings like 'get-price' or 'get-price-change', which might also provide market-related data for cryptocurrency pairs.

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 such as 'get-price' or 'get-historical-ohlcv'. It mentions the resource but lacks explicit instructions on scenarios, prerequisites, or exclusions, leaving usage context implied rather than clearly defined.

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