Skip to main content
Glama
aiordanescu

ib-gateway-mcp

by aiordanescu

Open orders

get_open_orders
Read-only

Retrieve the account's working orders with status, filled and remaining quantities, and prices. Optionally include orders from other API clients or only those placed by this server.

Instructions

List the account's working orders: status, filled/remaining quantity and prices.

`modifiable` is true only for orders this server placed (same API client id): only
those can be modified or cancelled with the order tools. Orders of other API clients
and manual TWS orders are shown for information. Filled and cancelled orders are
left out; see get_completed_orders. When the gateway's API is read-only (get_health:
api_read_only), IBKR refuses the request for this server's orders alone, so
include_other_clients=false reads every client's orders and keeps this server's;
`note` says so. Errors: ib_api_error 321, at once, if IBKR refuses open orders
altogether on a read-only API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountNoIBKR account id, e.g. DU1234567. Omit to use the default account; list_accounts shows which accounts are allowed.
include_other_clientsNoAlso list orders placed by other API clients and manually in TWS (default). False lists only the orders this server placed.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNoSet when the orders were read another way than asked: on a read-only gateway API, this server's own orders come from every client's list, filtered by client id.
as_ofYesWhen this server read the values (UTC).
ordersYes
accountYes
include_other_clientsYesWhether orders of other API clients and manual TWS orders were included.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A5/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint. The description adds essential behavioral detail: modifiable is true only for orders placed by this same server/client, other clients' orders are informational only, and IBKR can refuse the request on a read-only API with error 321 and a specific workaround. This is exactly the kind of context structured annotations cannot convey.

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 dense but every sentence earns its place: scope and output fields, modifiability semantics, the completed-orders alternative, the read-only edge case, and the error code. The core purpose is front-loaded with no filler.

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

Completeness5/5

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

For a read-only listing tool with no required parameters and an output schema present, the description covers all needed context: what is returned, what is excluded, which sibling to use instead, the read-only failure mode, and the fallback behavior. Nothing essential is missing.

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

Parameters5/5

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

Schema coverage is 100%, but the description still adds meaning beyond it: it explains the modifiable constraint tied to the API client and precisely what include_other_clients=false does under read-only gateway conditions. This goes well beyond the schema's one-line parameter descriptions.

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

Purpose5/5

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

The description opens with 'List the account's working orders' and specifies the returned fields: status, filled/remaining quantity, and prices. It explicitly contrasts with get_completed_orders by stating which order states are excluded, making it clearly distinguishable from the large sibling set.

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

Usage Guidelines5/5

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

The description states this tool shows working orders only, that filled/cancelled orders are excluded, and directs the agent to get_completed_orders for those. It also explains when include_other_clients=false is needed under a read-only API, giving concrete routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.