Skip to main content
Glama
snjyor

Binance Cryptocurrency MCP

by snjyor

get_24hr_ticker

Retrieve 24-hour price change statistics for cryptocurrency trading pairs on Binance, including current price, volume, and percentage changes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolNoTrading pair symbol, e.g. BTCUSDT
symbolsNoArray of multiple trading pair symbols

Implementation Reference

  • Handler function that fetches 24-hour price change statistics from Binance API endpoint /api/v3/ticker/24hr for a given symbol or multiple symbols, returns formatted JSON response or error message.
        try {
            let params = {};
            if (args.symbol) {
                params = { symbol: args.symbol };
            } else if (args.symbols) {
                params = { symbols: JSON.stringify(args.symbols) };
            }
    
            const response = await axios.get(`${BASE_URL}/api/v3/ticker/24hr`, {
                params,
                proxy: getProxy(),
            });
            return {
                content: [{ type: "text", text: JSON.stringify(response.data, null, 2) }]
            };
        } catch (error: any) {
            return {
                content: [{ type: "text", text: `Failed to get 24hr price statistics: ${error.message}` }],
                isError: true
            };
        }
    }
  • Input schema for get_24hr_ticker tool using Zod, allowing optional single symbol or array of symbols.
        symbol: z.string().optional().describe("Trading pair symbol, e.g. BTCUSDT"),
        symbols: z.array(z.string()).optional().describe("Array of multiple trading pair symbols")
    },
    async (args: { symbol?: string; symbols?: string[] }) => {
  • src/index.ts:236-264 (registration)
    Registration of the get_24hr_ticker tool in the registerTools function using McpServer.tool method.
        "get_24hr_ticker",
        {
            symbol: z.string().optional().describe("Trading pair symbol, e.g. BTCUSDT"),
            symbols: z.array(z.string()).optional().describe("Array of multiple trading pair symbols")
        },
        async (args: { symbol?: string; symbols?: string[] }) => {
            try {
                let params = {};
                if (args.symbol) {
                    params = { symbol: args.symbol };
                } else if (args.symbols) {
                    params = { symbols: JSON.stringify(args.symbols) };
                }
    
                const response = await axios.get(`${BASE_URL}/api/v3/ticker/24hr`, {
                    params,
                    proxy: getProxy(),
                });
                return {
                    content: [{ type: "text", text: JSON.stringify(response.data, null, 2) }]
                };
            } catch (error: any) {
                return {
                    content: [{ type: "text", text: `Failed to get 24hr price statistics: ${error.message}` }],
                    isError: true
                };
            }
        }
    );
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

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

Tool has no description.

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/snjyor/binance-mcp'

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