Skip to main content
Glama
nadavgb-atom

ib-async-mcp

by nadavgb-atom
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

get_account_values

Retrieve account balances, margin details, and other financial metrics from Interactive Brokers through the ib-async-mcp server interface.

Instructions

Get account values (balance, margin, etc.).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountNoAccount ID (optional)

Implementation Reference

  • src/ib_async_mcp/server.py:479-481 (handler)
    Handler for the get_account_values tool, which retrieves account values using ib.accountValues.
    if name == "get_account_values":
    values = ib.accountValues(args.get("account", ""))
    return [{"account": v.account, "tag": v.tag, "value": v.value, "currency": v.currency} for v in values]
  • src/ib_async_mcp/server.py:96-105 (schema)
    MCP tool registration for get_account_values with inputSchema defining an optional account string.
    Tool(
    name="get_account_values",
    description="Get account values (balance, margin, etc.).",
    inputSchema={
        "type": "object",
        "properties": {
            "account": {"type": "string", "description": "Account ID (optional)"},
        },
    },
),

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden. While it lists data categories (balance, margin), it doesn't disclose read-only status, error behaviors, or whether omitting the account parameter returns all accounts or a default account.

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 brief single sentence with no filler. Every word earns its place. However, given the complexity of sibling tools and optional parameters, extreme breveness may underserve the agent.

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?

Adequate for a simple read operation with one parameter, but lacks differentiation from the server's extensive suite of account-related tools. Without an output schema, the 'etc.' leaves return value ambiguity.

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 has 100% coverage (account ID described as optional), establishing baseline 3. The description adds minimal additional semantics about the parameter itself, such as expected format or default behavior when omitted.

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

Purpose4/5

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

Clear verb and resource with specific examples (balance, margin). However, it doesn't differentiate from siblings like get_account_summary or get_portfolio which may overlap in functionality.

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 versus get_accounts, get_account_summary, or get_portfolio. 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