ib-gateway-mcp

SMART components

get_smart_components

Read-only

Expand a SMART BBO exchange code into the component exchanges with IBKR single-letter codes. Use this to identify which exchanges provide the best bid and offer from a quote's bbo_exchange code.

Instructions

Expand a SMART BBO exchange code into the exchanges behind it.

Quotes on SMART-routed contracts carry a `bbo_exchange` code; this lists the
exchanges it stands for, each with IBKR's single-letter code, which tells you where the
best bid and offer come from. The code only comes from market data (get_quotes needs
a market data subscription or delayed data). When IBKR returns no exchanges (e.g.
outside trading hours, or for a code not taken from a quote) the call fails with
not_found.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`bbo_exchange`	Yes	The bbo_exchange code from a quote (get_quotes), e.g. '9c0001'.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`components`	Yes
`bbo_exchange`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 23, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds valuable behavioral context: the data source dependency (market data subscription), the failure mode (not_found), and the meaning of the returned codes. It doesn't detail the output schema, but an output schema exists, so that burden is reduced.

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?

Three sentences, each earning its place: the core action, the data dependency and output meaning, and the failure condition. Front-loaded with the main verb and resource, 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 single-parameter read-only tool with a full output schema, the description covers the source of the input, the failure mode, and the meaning of the output. Nothing an agent needs to decide whether to call it and what to expect is missing.

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?

Schema description coverage is 100%, so the schema already documents the parameter. The description adds context by explaining where the bbo_exchange code comes from (get_quotes) and giving an example ('9c0001'), which helps the agent understand the parameter's provenance and format beyond the schema's generic description.

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 states a specific verb ('Expand') and resource ('SMART BBO exchange code'), and explains the output: the exchanges behind the code with IBKR's single-letter codes. It clearly distinguishes itself from get_quotes (which produces the bbo_exchange code) and from other market-data tools.

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 explicitly says the bbo_exchange code comes from market data via get_quotes, and that a market data subscription or delayed data is required. It also states when the call fails (outside trading hours, or for a code not taken from a quote), giving the agent clear conditions for use and failure expectations.

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

Deploy Server