Skip to main content
Glama
Sign In
Interactive Brokers MCP Server

Interactive Brokers MCP Server

by code-rabi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_live_orders

Retrieve all live or open orders to monitor and validate trade execution. Use for confirming market orders after placement.

Instructions

Get all live/open orders for monitoring and validation. Usage: {} for all accounts or { "accountId": "<id>" } for a specific account. This is the recommended way to validate that market orders were executed successfully after placing them.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_live_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.21.3
  2. Removedv1.15.1
  3. Addedv1.0.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations provided, so description must cover behavioral traits. It implies read-only but does not explicitly state safety, authentication needs, or rate limits. Lacks disclosure of side effects or limitations.

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?

Two sentences with a usage example, no wasted words. Front-loaded with the primary purpose and immediately usable information.

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

Completeness3/5

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

Given no output schema, the description does not describe the return format. It covers the core functionality well but omits details on response structure and edge cases. Acceptable for a simple list tool but incomplete for richer context.

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?

With 0% schema description coverage, the description compensates by explaining the optional 'accountId' parameter and its effect (all accounts vs. specific). Adds clear meaning beyond the schema's type-only specification.

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 'get' and the resource 'live/open orders' with a defined purpose 'for monitoring and validation.' It distinguishes from 'get_order_status' by focusing on live orders, though not explicitly differentiating from all siblings.

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

Usage Guidelines4/5

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

Provides concrete usage examples and a specific recommendation for validating market orders after placement. Does not explicitly state when not to use or list alternatives, but the context is clear.

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

Deploy Server

Other Tools