Skip to main content
Glama
nadavgb-atom

ib-async-mcp

by nadavgb-atom

get_portfolio

Retrieve portfolio positions with current market values from Interactive Brokers accounts to monitor investment performance and asset allocation.

Instructions

Get portfolio positions with market values.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountNoAccount ID (optional)

Implementation Reference

  • The handler logic for the 'get_portfolio' tool, which fetches portfolio items from the IB interface and returns them formatted as a list of dictionaries.
    if name == "get_portfolio":
        items = ib.portfolio(args.get("account", ""))
        return [{
            "symbol": p.contract.symbol,
            "sec_type": p.contract.secType,
            "position": p.position,
            "market_price": p.marketPrice,
            "market_value": p.marketValue,
            "average_cost": p.averageCost,
            "unrealized_pnl": p.unrealizedPNL,
            "realized_pnl": p.realizedPNL,
            "account": p.account,
        } for p in items]
  • Registration of the 'get_portfolio' tool definition, including its name, description, and input schema.
    Tool(
        name="get_portfolio",
        description="Get portfolio positions with market values.",
        inputSchema={
            "type": "object",
            "properties": {
                "account": {"type": "string", "description": "Account ID (optional)"},
            },
        },
    ),
Behavior2/5

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

No annotations provided, so description carries full burden. While 'market values' indicates current valuation data, critical behavioral details are missing: data freshness (real-time vs delayed), default account behavior when parameter omitted, caching policies, or error conditions.

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?

Extremely concise at 5 words with no redundancy. Single sentence structure is efficient, though arguably under-specified given domain complexity.

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?

For a financial trading tool with 20+ siblings including `get_positions`, the description is insufficient. Missing: explicit differentiation from related position queries, output structure guidance (no output schema exists), and multi-account behavior.

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?

Schema coverage is 100% (account parameter fully documented). Description adds no parameter context, but baseline 3 applies when schema does the heavy lifting. No explanation of account ID format or omission behavior.

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

Purpose3/5

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

States specific verb 'Get' and resource 'portfolio positions with market values', distinguishing content from raw positions. However, fails to explicitly differentiate from sibling tool `get_positions`, which is critical given the overlapping semantics in trading contexts.

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?

Provides no guidance on when to use this versus siblings like `get_positions`, `get_account_values`, or `get_account_summary`. No mention of prerequisites or behavior when the optional account parameter is 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