Skip to main content
Glama

binance_account_openOrders

List open orders for a specific trading symbol on Binance to monitor pending transactions and manage active positions.

Instructions

List open orders for a symbol.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYes

Implementation Reference

  • The main handler implementation for the 'binance_account_openOrders' tool. It parses input, calls binance.openOrders with the symbol, and returns the data or throws a tool error.
    export const tool_open_orders: BinanceTool = {
      name: "binance_account_openOrders",
      description: "List open orders for a symbol.",
      parameters: openOrdersSchema,
      async run(input) {
        const params = openOrdersSchema.parse(input);
        try {
          const res = await binance.openOrders(params.symbol, withCommonParams({}));
          return res.data;
        } catch (err) {
          throw toToolError(err);
        }
      }
    };
  • Zod schema defining the input parameters for the tool: an object with a required 'symbol' string.
    const openOrdersSchema = z.object({ symbol: z.string().min(1) });
  • src/index.ts:15-40 (registration)
    The tool 'tool_open_orders' (binance_account_openOrders) is included in the tools array and registered to the MCP server via a forEach loop that adds each tool with its name, description, parameters, and a wrapper execute function calling the tool's run method.
    const tools = [
      tool_market_price,
      tool_market_klines,
      tool_exchange_info,
      tool_account_balances,
      tool_open_orders,
      tool_place_order,
      tool_cancel_order,
    ];
    
    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;
          }
        },
      });
    });
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 action ('List open orders') but does not cover critical aspects like authentication needs, rate limits, error handling, or response format. This leaves significant gaps for a tool interacting with a financial API.

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 with no wasted words, making it highly concise and front-loaded. It directly states the tool's purpose without unnecessary elaboration.

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 a Binance API tool with no annotations, no output schema, and low parameter documentation, the description is incomplete. It lacks details on authentication, rate limits, error cases, and return values, which are essential for safe and effective use.

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

Parameters2/5

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

The schema description coverage is 0%, and the description only mentions 'for a symbol' without explaining what the symbol parameter represents (e.g., trading pair format like 'BTCUSDT'), its constraints, or examples. This fails to compensate for the lack of schema documentation.

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 verb ('List') and resource ('open orders for a symbol'), making the purpose specific and understandable. However, it does not explicitly differentiate from sibling tools like binance_account_balances or binance_market_price, 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, such as binance_trade_cancelOrder for managing orders or binance_market_price for price data. It lacks explicit context, prerequisites, or exclusions, leaving usage unclear.

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