Skip to main content
Glama
Sign In
Interactive Brokers MCP Server

Interactive Brokers MCP Server

by code-rabi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_market_data

Retrieve real-time market data for any stock symbol, with optional exchange specification, to inform trading decisions.

Instructions

Get real-time market data. Usage: { "symbol": "AAPL" } or { "symbol": "AAPL", "exchange": "NASDAQ" }.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "get_market_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes
exchangeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.21.3
  2. Removedv1.15.1
  3. Changed2 schema fields changedv1.0.0
    • removedInput schema / properties / exchange / description
      Removed value: -"Exchange (optional)"
    • removedInput schema / properties / symbol / description
      Removed value: -"Trading symbol (e.g., AAPL, TSLA)"
  4. First observed

TDQS

A3.7/5.0
Behavior2/5

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

No annotations provided, so the description carries full burden. It mentions 'real-time' but lacks details on rate limits, data freshness, or error handling. Behavioral transparency is minimal.

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 short sentences, front-loaded with purpose followed by examples. No wasted words.

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

Completeness4/5

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

For a simple 2-parameter tool with no output schema, the description covers the essential purpose and usage. Could add return format or error information, but sufficient for basic understanding.

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?

With 0% schema coverage, the description must compensate. It shows usage examples but adds no additional semantics beyond parameter names and types. No format or constraints explained.

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 clearly states the tool retrieves real-time market data, with the verb 'Get' and specific resource. It is distinct from sibling tools like place_order or get_account_info.

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?

The description provides explicit usage examples showing required and optional parameters. It implies when to use the tool but does not specify when not to use or mention alternatives.

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