ib-gateway-mcp

Accounts in scope

list_accounts

Read-only

List available IBKR accounts and identify the default account for API calls. Clarifies which accounts need explicit selection and which are paper trading accounts.

Instructions

List the IBKR accounts this server may use, and which one is the default.

Account-scoped tools use `default_account` when called without an account. If it is
null, the login manages several accounts and you must pass one explicitly. Paper
accounts start with D. Accounts outside the server's allowlist are only counted
(`other_managed_accounts`), never named, and cannot be used.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`accounts`	Yes
`default_account`	No	Account used when none is given; None means pass one explicitly.
`other_managed_accounts`	No	How many more accounts this login manages outside the allowlist.

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 default_account behavior, the null case, paper account naming convention (D prefix), and the restriction that non-allowlisted accounts are only counted and never named. This goes beyond the annotations.

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?

The description is compact and front-loaded: the first sentence states the core purpose, and subsequent sentences add essential behavioral details without redundancy. Every sentence earns its place.

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 parameterless read-only tool with an output schema, the description covers everything an agent needs: what the tool returns, how to interpret the default_account field, and the constraints on account usage. The output schema presumably details the return structure, so the description need not repeat it.

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?

The tool has zero parameters, so the schema provides no parameter semantics. The description compensates by explaining the output's key fields (default_account, other_managed_accounts) and their implications, which is the relevant semantic content for a parameterless tool.

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 lists IBKR accounts the server may use and identifies the default. It distinguishes itself from sibling account-related tools by focusing on account scope rather than account values or summaries.

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 explains when to use this tool: to determine which account to pass to account-scoped tools, especially when default_account is null. It also clarifies that accounts outside the allowlist cannot be used, providing clear guidance for tool selection.

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

Deploy Server