Skip to main content
Glama
jianchundev

Binance Cryptocurrency MCP

by jianchundev

get_24hr_ticker

Retrieve 24-hour price change statistics for cryptocurrency trading pairs from Binance. Use this tool to monitor market movements, analyze price fluctuations, and track trading pair performance over a full day period.

Input Schema

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

Implementation Reference

  • The main handler function that executes the get_24hr_ticker tool. It accepts optional 'symbol' or 'symbols' parameters, constructs the appropriate request parameters, makes an HTTP GET request to Binance's /api/v3/ticker/24hr endpoint with proxy support, and returns the 24hr price statistics as formatted JSON or an error message.
    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,
                ...getProxyConfig(),
            });
            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
            };
        }
    }
  • Zod schema definition for the get_24hr_ticker tool input parameters. Defines two optional parameters: 'symbol' for a single trading pair (e.g., BTCUSDT) and 'symbols' for an array of multiple trading pair 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")
    },
  • src/index.ts:237-267 (registration)
    Complete registration of the get_24hr_ticker tool using server.tool() method. Includes the tool name, input validation schema, and the async handler function that makes the API call to Binance.
    // 24hr Price Change Statistics
    server.tool(
        "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,
                    ...getProxyConfig(),
                });
                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
                };
            }
        }
    );
  • Helper function getProxyConfig() that configures proxy settings for HTTP requests. It prioritizes SOCKS5 proxy (if SOCKS_PROXY or SOCKS5_PROXY env var is set), falls back to HTTP proxy (if HTTP_PROXY or HTTPS_PROXY env var is set), and returns an empty object if no proxy is configured.
    function getProxyConfig(): any {
        // 优先使用SOCKS5代理
        if (socksProxyURL) {
            try {
                const agent = new SocksProxyAgent(socksProxyURL);
                return { httpsAgent: agent, httpAgent: agent };
            } catch (error) {
                console.error(`Failed to create SOCKS proxy agent: ${error}`);
            }
        }
        
        // 回退到HTTP代理
        if (httpProxyURL) {
            try {
                const urlInfo = new URL(httpProxyURL);
                return {
                    proxy: {
                        host: urlInfo.hostname,
                        port: parseInt(urlInfo.port) || (urlInfo.protocol === 'https:' ? 443 : 80),
                        protocol: urlInfo.protocol.replace(":", "")
                    }
                };
            } catch (error) {
                console.error(`Failed to parse HTTP proxy URL: ${error}`);
            }
        }
        
        return {};
    }
  • Base configuration constants used by the get_24hr_ticker handler: BASE_URL for the Binance API endpoint, and environment variable configurations for HTTP and SOCKS proxy support.
    const BASE_URL = "https://api.binance.com";
    
    // 支持多种代理类型
    const httpProxyURL = process.env.HTTP_PROXY || process.env.HTTPS_PROXY;
    const socksProxyURL = process.env.SOCKS_PROXY || process.env.SOCKS5_PROXY;
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/jianchundev/binance-mcp'

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