Loading ToolBench

Reading the current corpus…

ibkr_core_mcp MCP server · D · ToolBench

ibkr_core_mcp

Interactive Brokers from Python, end to end: complete Client Portal Web API connectivity (78 endpoints, REST + WebSocket, Docker gateway), market and historical data management with a Google Drive cloud cache, Flex statements, 44 Claude tools + MCP server for any Python or MCP client, backtests and analytics — orders behind Touch ID + confirmation.

<=2025-11-25STDIO23 tools

59/100

Definition Quality72

Protocol Readiness42

Supportability50

Spec posture

Inferred effective spec <=2025-11-25·current baseline 2026-07-28

Static source inference · medium confidence · detected: Logging, Dynamic Client Registration

Deprecated protocol patterns detected

Summary

23 tools with mostly complete schemas and descriptions, but significant gaps in parameter documentation and output schema clarity. Tool names follow verb_noun convention well (get_*, place_*, add_*). Descriptions average ~80 chars, below the 194-char baseline for A+ tools. Most parameters have type and description, but many lack constraints (enums, ranges, formats). Output schemas are not documented, LLMs cannot predict response structure. Error handling is minimal; no recovery guidance. Security-sensitive tools (place_order, cancel_order) lack confirmation patterns. Web scraping tools (fetch_page, crawl_site, firecrawl_search) are domain-misaligned for a financial broker MCP.

Tools (23)

add_price_alertwriteauthsource verified82/100

Create a price alert that fires when a symbol crosses a threshold. direction must be 'above' or 'below'.

add_to_watchlistwriteauth50/100

Add a symbol to a watchlist

cancel_orderreversibleauth50/100

Cancel an existing order

crawl_siteread onlysource verified62/100

Crawl a website and extract content

fetch_pageread onlysource verified62/100

Fetch and parse a web page

firecrawl_searchread onlyauthsource verified60/100

Search using Firecrawl API

get_account_summaryread onlyauthsource verified78/100

Get account summary and balance information

get_accounts

Issues (5)

CRITICALresponse-shaper ↗

Output schemas not documented. LLMs cannot predict response structure for any of the 23 tools. Responses must include pagination info (total_count, next_cursor), field types, and chaining IDs (e.g., account_id for downstream calls). Currently undocumented.

get_accountsget_positionsget_tradesget_market_dataget_historical_dataget_watchlistget_flex_tradesget_account_summaryget_portfolio_allocationget_pnlget_price_alerts

CRITICALconfirmation-request ↗

Irreversible operations (place_order, cancel_order, sync_flex_trades) lack confirmation/dry-run patterns. Agents can execute destructive trades without user confirmation, risking financial loss.

place_ordercancel_ordersync_flex_trades

HIGHconstrained-input ↗

Parameter constraints missing. place_order lacks enum for order_type (MKT, LMT, STP, etc.), quantity/price ranges, or validation rules. run_backtest period param accepts free-form strings ('1d', '1w', '1m') without enum. LLMs will hallucinate invalid values.

Recommendations

Document output schemas for all 23 tools. Include field names, types, pagination (total_count, next_cursor), and chaining IDs (e.g., account_id, order_id). Example: get_positions should return [{account_id, symbol, quantity, price, pnl, ...}, ...] with total_count.
Add confirmation/dry-run pattern to place_order and cancel_order. Implement a preview_order tool that returns estimated execution details without committing, or add a 'confirm' parameter requiring explicit user approval before execution.
Constrain parameters with enums and ranges. place_order.order_type → enum [MKT, LMT, STP, TRAIL]. get_historical_data.period → enum [1d, 1w, 1m, 3m, 1y]. add_price_alert.direction already has enum; apply same pattern to all constrained params.
Remove or isolate web scraping tools (fetch_page, crawl_site, search_site, firecrawl_search). They are out of scope for a financial broker MCP and introduce security/compliance risk. If retained, move to a separate 'web_tools' MCP or gate behind explicit user opt-in.
Add error handling with recovery guidance. Example: place_order fails → return '{error: "Insufficient buying power", recovery: "Check account balance with get_account_summary() or reduce order quantity"}'. Categorize errors as retryable, user-fixable, or fatal.

Spec posture evidence

Inferred effective spec: <=2025-11-25.

Relies on Logging (deprecated) - log to stderr or use OpenTelemetry

Score history

Overall score trend

First recorded score · v2 rubric

59/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	D	59	<=2025-11-25	v2