Skip to main content
Glama
snjyor

Binance Cryptocurrency MCP

by snjyor

get_trading_day_ticker

Retrieve trading day ticker data for cryptocurrency pairs from Binance, providing price information and market statistics for specified symbols.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolNoTrading pair symbol, e.g. BTCUSDT
symbolsNoArray of multiple trading pair symbols
timeZoneNoTime zone, default 0
typeNoReturn data type, FULL or MINI

Implementation Reference

  • The handler function for the 'get_trading_day_ticker' tool. It constructs parameters from input args, makes an HTTP GET request to the Binance API endpoint /api/v3/ticker/tradingDay using axios, and returns the JSON response or an error message.
    async (args: { symbol?: string; symbols?: string[]; timeZone?: number; type?: "FULL" | "MINI" }) => {
        try {
            let params: any = {};
            if (args.symbol) {
                params.symbol = args.symbol;
            } else if (args.symbols) {
                params.symbols = JSON.stringify(args.symbols);
            }
            if (args.timeZone) params.timeZone = args.timeZone;
            if (args.type) params.type = args.type;
    
            const response = await axios.get(`${BASE_URL}/api/v3/ticker/tradingDay`, {
                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 trading day ticker: ${error.message}` }],
                isError: true
            };
        }
    }
  • Zod schema defining the input parameters for the 'get_trading_day_ticker' tool, including optional symbol or symbols array, timeZone, and type.
    {
        symbol: z.string().optional().describe("Trading pair symbol, e.g. BTCUSDT"),
        symbols: z.array(z.string()).optional().describe("Array of multiple trading pair symbols"),
        timeZone: z.number().optional().describe("Time zone, default 0"),
        type: z.enum(["FULL", "MINI"]).optional().describe("Return data type, FULL or MINI")
    },
  • src/index.ts:267-300 (registration)
    Registration of the 'get_trading_day_ticker' tool using server.tool(), including schema and handler.
    server.tool(
        "get_trading_day_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"),
            timeZone: z.number().optional().describe("Time zone, default 0"),
            type: z.enum(["FULL", "MINI"]).optional().describe("Return data type, FULL or MINI")
        },
        async (args: { symbol?: string; symbols?: string[]; timeZone?: number; type?: "FULL" | "MINI" }) => {
            try {
                let params: any = {};
                if (args.symbol) {
                    params.symbol = args.symbol;
                } else if (args.symbols) {
                    params.symbols = JSON.stringify(args.symbols);
                }
                if (args.timeZone) params.timeZone = args.timeZone;
                if (args.type) params.type = args.type;
    
                const response = await axios.get(`${BASE_URL}/api/v3/ticker/tradingDay`, {
                    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 trading day ticker: ${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