Skip to main content
Glama
qeinfinity

Binance MCP Server

get_futures_open_interest

Retrieve current open interest data for Binance futures trading pairs to analyze market sentiment and liquidity.

Instructions

Get current open interest for a futures trading pair

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesTrading pair symbol (e.g., BTCUSDT)

Implementation Reference

  • The MCP server tool handler that processes calls to 'get_futures_open_interest', validates input using isFuturesDataParams, extracts the symbol, calls the rest connector's getFuturesOpenInterest method, and returns the data as formatted JSON.
    case "get_futures_open_interest": {
      if (!isFuturesDataParams(request.params.arguments)) {
        throw new Error('Invalid futures data parameters');
      }
      const { symbol } = request.params.arguments;
      const data = await restConnector.getFuturesOpenInterest(symbol);
      return {
        content: [{
          type: "text",
          text: JSON.stringify(data, null, 2)
        }]
      };
    }
  • src/index.ts:80-93 (registration)
    Tool registration in the ListToolsRequestSchema handler, defining the name, description, and input schema (object with required 'symbol' string).
    {
      name: "get_futures_open_interest",
      description: "Get current open interest for a futures trading pair",
      inputSchema: {
        type: "object",
        properties: {
          symbol: { 
            type: "string", 
            description: "Trading pair symbol (e.g., BTCUSDT)" 
          }
        },
        required: ["symbol"]
      }
    },
  • Core helper method in BinanceRestConnector class that performs the HTTP GET request to Binance futures '/openInterest' endpoint using axios with retry logic, logging, and error handling, returning the raw API response data.
    public async getFuturesOpenInterest(symbol: string): Promise<any> {
      try {
        logger.info(`Getting futures open interest for ${symbol}`);
        const response = await this.executeWithRetry(() =>
          this.axiosInstance.get(`${config.FUTURES_REST_URL}/openInterest`, {
            params: { symbol: symbol.toUpperCase() }
          })
        );
        logger.info('Successfully fetched open interest data');
        return response.data;
      } catch (error) {
        logger.error('Error fetching open interest:', error);
        throw new APIError('Failed to fetch open interest data', error as Error);
      }
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states what the tool does but doesn't describe any behavioral traits such as rate limits, authentication requirements, response format, or potential errors. This is inadequate for a tool with zero annotation coverage.

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

Conciseness5/5

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

The description is a single, efficient sentence that directly states the tool's purpose without any wasted words. It's appropriately sized and front-loaded, making it easy for an agent to parse quickly.

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 lack of annotations and output schema, the description is incomplete. It doesn't address what the tool returns (e.g., numerical value, timestamp, additional metadata) or any behavioral aspects like error handling. For a tool with no structured data beyond the input schema, this leaves significant gaps for an agent.

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 schema description coverage is 100%, with the parameter 'symbol' fully documented in the input schema. The description doesn't add any meaningful semantics beyond what the schema already provides (e.g., it doesn't clarify format constraints or provide examples beyond the schema's 'e.g., BTCUSDT'), so it meets the baseline for high schema coverage.

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

Purpose4/5

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

The description clearly states the action ('Get current open interest') and the resource ('for a futures trading pair'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'get_futures_funding_rate' or 'get_market_data', which prevents a perfect score.

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 like 'get_futures_funding_rate' or 'get_market_data'. There's no mention of prerequisites, context, or exclusions, leaving the agent to infer usage from the tool name alone.

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

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