Skip to main content
Glama
nadavgb-atom

ib-async-mcp

by nadavgb-atom
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

get_account_summary

Retrieve account summary information from Interactive Brokers, including balances, positions, and performance metrics for portfolio management.

Instructions

Get account summary.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountNoAccount ID (optional)

Implementation Reference

  • src/ib_async_mcp/server.py:483-486 (handler)
    The handler for the 'get_account_summary' tool, which fetches account summary data from the Interactive Brokers API.
    if name == "get_account_summary":
    summary = ib.accountSummary(args.get("account", ""))
    return [{"account": v.account, "tag": v.tag, "value": v.value, "currency": v.currency} for v in summary]
  • src/ib_async_mcp/server.py:107-115 (registration)
    The MCP tool registration for 'get_account_summary'.
        name="get_account_summary",
    description="Get account summary.",
    inputSchema={
        "type": "object",
        "properties": {
            "account": {"type": "string", "description": "Account ID (optional)"},
        },
    },
),

Tool Definition Quality

C2.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. It does not specify what data the summary contains (balances, positions, equity), whether the data is real-time or cached, or if specific permissions are required. Only implies read-only behavior via the verb 'Get'.

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

Conciseness3/5

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

Extremely brief (3 words), avoiding verbosity. However, the single sentence does not earn its place as it adds minimal value beyond the tool name itself. Front-loading is irrelevant given the lack of content.

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?

Inadequate for a financial/trading domain tool with no output schema. Should explainsummary contents and account selection behavior when the optional parameter is omitted. Leaves critical gaps for an agent trying to select between multiple account-related endpoints.

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

Parameters3/5

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

Input schema has 100% description coverage (account: 'Account ID (optional)'). Since the schema fully documents the single optional parameter, baseline score is 3. Description adds no additional semantic context (e.g., default account behavior, ID format).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description 'Get account summary' essentially restates the tool name (tautology). While it indicates a read operation on an account resource, it fails to distinguish from sibling tools like get_accounts, get_account_values, or get_portfolio, leaving the specific scope ambiguous.

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 provided on when to use this tool versus alternatives (e.g., get_account_values for specific metrics or get_portfolio for holdings). The optional nature of the 'account' parameter is unexplained—description does not indicate what happens when omitted.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nadavgb-atom/ib-async-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server