Skip to main content
Glama

binance_market_exchangeInfo

Retrieve exchange information and symbol filters to understand trading parameters and restrictions on Binance.

Instructions

Get exchange information including filters per symbol.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler implementation of the 'binance_market_exchangeInfo' tool. Defines the tool object with name, description, parameters schema reference, and the async run() function that fetches exchangeInfo from the binance client and returns the data, handling errors with toToolError.
    export const tool_exchange_info: BinanceTool = {
      name: "binance_market_exchangeInfo",
      description: "Get exchange information including filters per symbol.",
      parameters: exchangeInfoSchema,
      async run() {
        try {
          const res = await binance.exchangeInfo();
          return res.data;
        } catch (err) {
          throw toToolError(err);
        }
      }
    };
  • Zod input schema for the tool (empty object since no parameters required).
    const exchangeInfoSchema = z.object({});
  • src/index.ts:15-23 (registration)
    The tools array that includes 'tool_exchange_info' which is then registered to the FastMCP server.
    const tools = [
      tool_market_price,
      tool_market_klines,
      tool_exchange_info,
      tool_account_balances,
      tool_open_orders,
      tool_place_order,
      tool_cancel_order,
    ];
  • src/index.ts:25-40 (registration)
    The registration loop that adds the 'binance_market_exchangeInfo' tool (and others) to the MCP server using server.addTool, wrapping the tool's run function in an execute handler with JSON formatting and error handling.
    tools.forEach((tool) => {
      server.addTool({
        name: tool.name,
        description: tool.description,
        parameters: tool.parameters,
        execute: async (args) => {
          try {
            const result = await tool.run(args);
            return JSON.stringify(result, null, 2);
          } catch (error) {
            const handled = error instanceof ToolError ? error : new ToolError((error as Error).message);
            throw handled;
          }
        },
      });
    });
  • Helper function toToolError used in the tool handler to convert errors (e.g., from Binance API) into standardized ToolError instances.
    export function toToolError(err: unknown): ToolError {
      const message = extractMessage(err);
      return new ToolError(message);
    }
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 the tool retrieves exchange information, implying a read-only operation, but doesn't cover critical aspects like rate limits, authentication requirements, error handling, or response format. This leaves significant gaps in understanding how the tool behaves in practice.

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 unnecessary words. It's front-loaded with the core action and resource, making it easy to parse quickly, which is ideal for a tool with no parameters.

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 for a tool that likely returns complex exchange data. It doesn't explain what 'exchange information' includes beyond 'filters per symbol', nor does it address behavioral traits like performance or limitations, leaving the agent under-informed for effective use.

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

Parameters4/5

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

The input schema has 0 parameters with 100% coverage, meaning no parameters are documented in the schema. The description doesn't add parameter details, which is appropriate since there are none to explain. It effectively conveys that this tool requires no inputs, aligning with the schema's emptiness.

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 tool's purpose with a specific verb ('Get') and resource ('exchange information including filters per symbol'), making it easy to understand what data it retrieves. However, it doesn't explicitly differentiate from sibling tools like 'binance_market_price' or 'binance_market_klines', which also provide market data but with different scopes.

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. It doesn't mention specific contexts, prerequisites, or exclusions, leaving the agent to infer usage based on the tool name and description alone, which is insufficient for optimal selection among similar market data tools.

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

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