Skip to main content
Glama
snjyor

Binance Cryptocurrency MCP

by snjyor

get_aggregate_trades

Retrieve aggregated cryptocurrency trade data for specific trading pairs, enabling analysis of market activity and price movements over time.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesTrading pair symbol, e.g. BTCUSDT
fromIdNoAggregate trade ID to start from
startTimeNoStart timestamp (milliseconds)
endTimeNoEnd timestamp (milliseconds)
limitNoNumber of trades to return, default 500, max 1000

Implementation Reference

  • The asynchronous handler function that calls the Binance API endpoint /api/v3/aggTrades to retrieve aggregate trades data, handles the response, and returns it as JSON or an error message.
    async (args: { symbol: string; fromId?: number; startTime?: number; endTime?: number; limit?: number }) => {
        try {
            const response = await axios.get(`${BASE_URL}/api/v3/aggTrades`, {
                params: {
                    symbol: args.symbol,
                    fromId: args.fromId,
                    startTime: args.startTime,
                    endTime: args.endTime,
                    limit: args.limit
                },
                proxy: getProxy(),
            });
            return {
                content: [{ type: "text", text: JSON.stringify(response.data, null, 2) }]
            };
        } catch (error: any) {
            return {
                content: [{ type: "text", text: `Failed to get aggregate trades: ${error.message}` }],
                isError: true
            };
        }
    }
  • Zod schema defining the input parameters for the get_aggregate_trades tool.
    {
        symbol: z.string().describe("Trading pair symbol, e.g. BTCUSDT"),
        fromId: z.number().optional().describe("Aggregate trade ID to start from"),
        startTime: z.number().optional().describe("Start timestamp (milliseconds)"),
        endTime: z.number().optional().describe("End timestamp (milliseconds)"),
        limit: z.number().optional().describe("Number of trades to return, default 500, max 1000")
    },
  • src/index.ts:104-134 (registration)
    Registration of the get_aggregate_trades tool using McpServer.tool method, specifying the tool name, input schema, and inline handler function.
        "get_aggregate_trades",
        {
            symbol: z.string().describe("Trading pair symbol, e.g. BTCUSDT"),
            fromId: z.number().optional().describe("Aggregate trade ID to start from"),
            startTime: z.number().optional().describe("Start timestamp (milliseconds)"),
            endTime: z.number().optional().describe("End timestamp (milliseconds)"),
            limit: z.number().optional().describe("Number of trades to return, default 500, max 1000")
        },
        async (args: { symbol: string; fromId?: number; startTime?: number; endTime?: number; limit?: number }) => {
            try {
                const response = await axios.get(`${BASE_URL}/api/v3/aggTrades`, {
                    params: {
                        symbol: args.symbol,
                        fromId: args.fromId,
                        startTime: args.startTime,
                        endTime: args.endTime,
                        limit: args.limit
                    },
                    proxy: getProxy(),
                });
                return {
                    content: [{ type: "text", text: JSON.stringify(response.data, null, 2) }]
                };
            } catch (error: any) {
                return {
                    content: [{ type: "text", text: `Failed to get aggregate trades: ${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