Skip to main content
Glama
nadavgb-atom

ib-async-mcp

by nadavgb-atom

get_open_orders

Retrieve all currently active orders from Interactive Brokers accounts to monitor trade execution status and manage positions.

Instructions

Get all open orders.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler logic for 'get_open_orders' that calls ib.openOrders() and serializes the result.
    if name == "get_open_orders":
        orders = ib.openOrders()
        return [serialize_object(o) for o in orders]
  • The Tool definition and registration for 'get_open_orders'.
    Tool(
        name="get_open_orders",
        description="Get all open orders.",
        inputSchema={"type": "object", "properties": {}},
    ),
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 but fails to clarify what 'open' means (pending, partially filled, submitted), whether the data is real-time or cached, or what return format to expect. It does not mention pagination, account scoping, or session requirements despite these being critical for trading APIs.

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 maximally concise at only four words, with no redundancy or filler content. The single sentence is front-loaded with the essential action and resource, making efficient use of space despite the resulting information gaps.

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 high domain complexity and complete absence of output schema or annotations, the description is inadequate. It fails to compensate for missing structured metadata by describing expected return values, error conditions, or the specific definition of 'open' orders required to distinguish this from similar order-state queries.

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 contains zero parameters, establishing a baseline score of 4. The description neither adds nor detracts from this baseline, as there are no parameter semantics to elaborate upon beyond the empty schema.

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 states a clear verb ('Get') and specific resource ('open orders'), accurately describing the core function. However, it lacks explicit differentiation from similar sibling tools like 'get_open_trades', 'get_executions', or 'get_fills', which is critical in this trading domain with numerous overlapping retrieval functions.

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 'get_open_trades' (positions) or 'get_executions' (filled orders). In a complex trading API with 30+ sibling tools, the absence of contextual usage boundaries leaves the agent without selection criteria.

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/nadavgb-atom/ib-async-mcp'

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