Skip to main content
Glama
jianchundev

Binance Cryptocurrency MCP

by jianchundev

get_rolling_window_ticker

Retrieve rolling window ticker data for Binance cryptocurrency trading pairs to analyze price movements over specified time intervals with customizable data detail levels.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolNoTrading pair symbol, e.g. BTCUSDT
symbolsNoArray of multiple trading pair symbols
windowSizeNoWindow size, e.g. 1m, 4h, 1d
typeNoReturn data type, FULL or MINI

Implementation Reference

  • The handler function that executes the get_rolling_window_ticker tool logic. It makes an HTTP GET request to Binance's /api/v3/ticker endpoint with the provided parameters (symbol, symbols, windowSize, type) and returns the rolling window price statistics.
    async (args: { symbol?: string; symbols?: string[]; windowSize?: string; 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.windowSize) params.windowSize = args.windowSize;
            if (args.type) params.type = args.type;
    
            const response = await axios.get(`${BASE_URL}/api/v3/ticker`, {
                params,
                ...getProxyConfig(),
            });
            return {
                content: [{ type: "text", text: JSON.stringify(response.data, null, 2) }]
            };
        } catch (error: any) {
            return {
                content: [{ type: "text", text: `Failed to get rolling window price statistics: ${error.message}` }],
                isError: true
            };
        }
    }
  • Schema definition for get_rolling_window_ticker tool parameters using zod validation. Defines optional parameters: symbol (string), symbols (array of strings), windowSize (string), and type (enum of 'FULL' or 'MINI').
    {
        symbol: z.string().optional().describe("Trading pair symbol, e.g. BTCUSDT"),
        symbols: z.array(z.string()).optional().describe("Array of multiple trading pair symbols"),
        windowSize: z.string().optional().describe("Window size, e.g. 1m, 4h, 1d"),
        type: z.enum(["FULL", "MINI"]).optional().describe("Return data type, FULL or MINI")
    },
  • src/index.ts:370-403 (registration)
    Registration of the get_rolling_window_ticker tool with the MCP server. The tool is registered within the registerTools function using server.tool() with its name, schema, and handler function.
    server.tool(
        "get_rolling_window_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"),
            windowSize: z.string().optional().describe("Window size, e.g. 1m, 4h, 1d"),
            type: z.enum(["FULL", "MINI"]).optional().describe("Return data type, FULL or MINI")
        },
        async (args: { symbol?: string; symbols?: string[]; windowSize?: string; 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.windowSize) params.windowSize = args.windowSize;
                if (args.type) params.type = args.type;
    
                const response = await axios.get(`${BASE_URL}/api/v3/ticker`, {
                    params,
                    ...getProxyConfig(),
                });
                return {
                    content: [{ type: "text", text: JSON.stringify(response.data, null, 2) }]
                };
            } catch (error: any) {
                return {
                    content: [{ type: "text", text: `Failed to get rolling window price statistics: ${error.message}` }],
                    isError: true
                };
            }
        }
    );
  • Helper function getProxyConfig() that configures proxy settings for HTTP requests. It supports SOCKS5 proxies (via SOCKS_PROXY or SOCKS5_PROXY env vars) and HTTP/HTTPS proxies (via HTTP_PROXY or HTTPS_PROXY env vars). Used by the get_rolling_window_ticker handler.
    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