Skip to main content
Glama
mixuechu

Binance MCP Server

by mixuechu

get_funding_rate_history

Retrieve historical funding rate data for Binance perpetual contracts to analyze market trends and manage trading positions effectively.

Instructions

Get funding rate history.

Args: symbol: Perpetual contract symbol. limit: Number of records to return (default 100).

Returns: Funding rate data list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYes
limitNo

Implementation Reference

  • The main handler function for the 'get_funding_rate_history' tool. It is registered via the @mcp.tool() decorator. This function queries the Binance Futures API for historical funding rates of a given symbol and limit, returning the JSON data or an error.
    @mcp.tool()
    def get_funding_rate_history(symbol: str, limit: int = 100) -> Any:
        """
        Get funding rate history.
    
        Args:
            symbol: Perpetual contract symbol.
            limit: Number of records to return (default 100).
    
        Returns:
            Funding rate data list.
        """
        url = "https://fapi.binance.com/fapi/v1/fundingRate"
        params = {"symbol": symbol, "limit": limit}
        response = requests.get(url, params=params)
        if response.status_code == 200:
            return response.json()
        return {"error": response.text}
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the tool 'gets' data (implying read-only) and describes basic parameters, but doesn't disclose important behavioral traits like rate limits, authentication requirements, data freshness/latency, error conditions, or pagination behavior. For a financial data tool with no annotation coverage, this leaves significant gaps in understanding how the tool behaves.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately concise with a clear structure: purpose statement followed by Args and Returns sections. Each sentence serves a purpose, though the initial purpose statement could be more informative. The formatting with clear sections helps readability, though the content within those sections could be more substantial.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of financial data retrieval, no annotations, no output schema, and 0% schema description coverage, the description is insufficiently complete. It doesn't explain what the returned 'Funding rate data list' contains (structure, fields, units), doesn't mention time ranges or date filtering, and provides minimal context about the domain (perpetual contracts). For a tool that presumably returns time-series financial data, this leaves too many questions unanswered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds basic parameter information beyond the schema, which has 0% description coverage. It explains that 'symbol' is for 'Perpetual contract symbol' and 'limit' controls 'Number of records to return (default 100)'. However, it doesn't provide format examples for the symbol parameter, explain what constitutes a 'record', or clarify the ordering of returned records. With 2 parameters and 0% schema coverage, this provides some but incomplete compensation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Get funding rate history' which is a tautology that essentially restates the tool name 'get_funding_rate_history'. While it mentions the resource (funding rate history), it lacks specificity about what 'funding rate' means in this context or what time period is covered. It doesn't distinguish this tool from potential siblings that might also retrieve funding data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. Given the sibling tools include 'get_trade_history' and 'get_symbol_price', there's no indication whether this tool should be used for historical analysis, real-time monitoring, or specific trading contexts. No prerequisites, exclusions, or comparison to other tools are mentioned.

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/mixuechu/binance-mcp'

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