Skip to main content
Glama
Sign In
IBKR MCP

IBKR MCP

by rodrigta
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ibkr_get_option_chain

Retrieve option chain expirations and strikes for any underlying symbol, specifying exchange and currency.

Instructions

Get option chain expirations and strikes for an underlying symbol.

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": "ibkr_get_option_chain"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes
exchangeNoSMART
currencyNoUSD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose any behavioral traits (e.g., read-only, required permissions, rate limits). The name implies a read operation, but this is not explicitly stated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, concise sentence that is front-loaded and efficient. However, it is too brief for a tool with 3 parameters and no output schema, missing important details.

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 tool has 3 parameters, no output schema, and no annotations, the description is incomplete. It does not explain the return format, pagination, or any behavioral aspects, leaving gaps for an agent.

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?

Schema coverage is 0%, so the description must compensate. It only mentions 'underlying symbol' for the required 'symbol' parameter, adding minimal value. No explanation for 'exchange' or 'currency' is given.

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 option chain expirations and strikes for an underlying symbol, using specific verb and resource. It distinguishes from sibling tools like ibkr_get_quote (quote data) and ibkr_place_option_order (order placement).

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?

No guidance is provided on when to use this tool versus alternatives, or any prerequisites. The description lacks context on typical usage scenarios, such as before placing an option order.

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