Skip to main content
Glama
jianchundev

Binance Cryptocurrency MCP

by jianchundev

get_historical_trades

Retrieve past cryptocurrency trades for a specific trading pair from Binance, allowing analysis of market activity and price movements over time.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesTrading pair symbol, e.g. BTCUSDT
limitNoNumber of trades to return, default 500, max 1000
fromIdNoTrade ID to start from, default returns the most recent trades

Implementation Reference

  • Complete implementation of get_historical_trades tool. This is the handler function that makes an HTTP GET request to Binance's /api/v3/historicalTrades endpoint with the provided symbol, limit, and fromId parameters. It includes error handling and uses proxy configuration. The tool requires a BINANCE_API_KEY environment variable for authentication.
    server.tool(
        "get_historical_trades",
        {
            symbol: z.string().describe("Trading pair symbol, e.g. BTCUSDT"),
            limit: z.number().optional().describe("Number of trades to return, default 500, max 1000"),
            fromId: z.number().optional().describe("Trade ID to start from, default returns the most recent trades")
        },
        async (args: { symbol: string; limit?: number; fromId?: number }) => {
            try {
                const response = await axios.get(`${BASE_URL}/api/v3/historicalTrades`, {
                    params: {
                        symbol: args.symbol,
                        limit: args.limit,
                        fromId: args.fromId
                    },
                    headers: {
                        "X-MBX-APIKEY": process.env.BINANCE_API_KEY || ""
                    },
                    ...getProxyConfig(),
                });
                return {
                    content: [{ type: "text", text: JSON.stringify(response.data, null, 2) }]
                };
            } catch (error: any) {
                return {
                    content: [{ type: "text", text: `Failed to get historical trades: ${error.message}` }],
                    isError: true
                };
            }
        }
    );
  • Zod schema definition for get_historical_trades tool parameters. Defines three optional parameters: symbol (trading pair), limit (number of trades to return, max 1000), and fromId (trade ID to start from).
    {
        symbol: z.string().describe("Trading pair symbol, e.g. BTCUSDT"),
        limit: z.number().optional().describe("Number of trades to return, default 500, max 1000"),
        fromId: z.number().optional().describe("Trade ID to start from, default returns the most recent trades")
    },
  • src/index.ts:73-103 (registration)
    Registration of get_historical_trades tool with the MCP server using server.tool() method. This includes the tool name, parameter schema, and the handler function.
    server.tool(
        "get_historical_trades",
        {
            symbol: z.string().describe("Trading pair symbol, e.g. BTCUSDT"),
            limit: z.number().optional().describe("Number of trades to return, default 500, max 1000"),
            fromId: z.number().optional().describe("Trade ID to start from, default returns the most recent trades")
        },
        async (args: { symbol: string; limit?: number; fromId?: number }) => {
            try {
                const response = await axios.get(`${BASE_URL}/api/v3/historicalTrades`, {
                    params: {
                        symbol: args.symbol,
                        limit: args.limit,
                        fromId: args.fromId
                    },
                    headers: {
                        "X-MBX-APIKEY": process.env.BINANCE_API_KEY || ""
                    },
                    ...getProxyConfig(),
                });
                return {
                    content: [{ type: "text", text: JSON.stringify(response.data, null, 2) }]
                };
            } catch (error: any) {
                return {
                    content: [{ type: "text", text: `Failed to get historical trades: ${error.message}` }],
                    isError: true
                };
            }
        }
    );
  • getProxyConfig() helper function used by the get_historical_trades handler. Supports both SOCKS5 and HTTP proxy configuration for making API requests through proxies.
    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 {};
    }
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