Skip to main content
Glama
Sign In
IBKR MCP

IBKR MCP

by rodrigta
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ibkr_get_account_summary

Retrieve account summary values including buying power and net liquidation to monitor your portfolio's financial status.

Instructions

Get account summary values (buying power, net liquidation, etc.).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ibkr_get_account_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idNo

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, so the description must fully disclose behavioral traits. It does not confirm that it is a read-only operation, mention authentication requirements, or describe behavior when account_id is null. The description assumes a read operation but lacks explicit transparency.

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 sentence that is front-loaded with the key purpose. It mentions examples, which adds value without unnecessary words. Slightly under-specified but not verbose.

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

Completeness3/5

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

Given the simplicity of the tool (one optional parameter, no output schema), the description provides minimal but acceptable context. It lists example return fields, which helps, but lacks a comprehensive list or structure of the summary values. For a read operation with no output schema, additional detail would improve completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter 'account_id' has no description in the schema (0% coverage). The tool description adds no additional meaning—it does not explain what 'null' means (e.g., defaults to current account) or provide context about valid account IDs. The schema alone is insufficient.

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 it retrieves account summary values, listing specific examples like buying power and net liquidation. It distinguishes itself from sibling tools like 'ibkr_get_positions' and 'ibkr_get_quote' by focusing on account-level aggregates.

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 explicit guidance on when to use this tool versus alternatives. The description does not mention exclusions or conditions (e.g., only works for the current user if account_id is null). The presence of sibling tools suggests alternatives, but no comparison is made.

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