Skip to main content
Glama
nadavgb-atom

ib-async-mcp

by nadavgb-atom

get_fills

Retrieve order execution details and trade confirmations from Interactive Brokers to monitor transaction history and track trade outcomes.

Instructions

Get order fills.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for the 'get_fills' tool, which fetches fills from IB and serializes them into a list of dictionaries.
    if name == "get_fills":
        fills = ib.fills()
        return [{
            "symbol": f.contract.symbol,
            "exec_id": f.execution.execId,
            "side": f.execution.side,
            "shares": f.execution.shares,
            "price": f.execution.price,
            "time": f.time.isoformat() if f.time else None,
            "commission": f.commissionReport.commission if f.commissionReport else None,
        } for f in fills]
  • The registration of the 'get_fills' tool in the tool list.
    Tool(
        name="get_fills",
        description="Get order fills.",
        inputSchema={"type": "object", "properties": {}},
    ),
Behavior2/5

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

No annotations are present, so the description must carry the full burden of behavioral disclosure. It fails to specify what time range of fills is returned (historical vs session), whether the data is real-time or cached, or any rate limiting considerations.

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?

The description consists of a single three-word sentence that is appropriately front-loaded, but it is under-specified rather than meaningfully concise. Every sentence should earn its place, and this one adds minimal value beyond the tool name itself.

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?

With no output schema provided and multiple similar trading data tools available (get_executions, get_open_orders), the description should clarify the specific scope and format of returned fill data. It fails to complete the picture for an agent deciding between related tools.

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?

Input schema contains zero parameters (empty properties object), which per rubric guidelines establishes a baseline score of 4. There are no parameters requiring semantic elaboration beyond what the trivial schema already provides.

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?

The description 'Get order fills' essentially restates the camelCase name 'get_fills' with spaces added. While it confirms the resource type (order fills), it fails to distinguish from the sibling tool 'get_executions' or specify scope (time range, account, etc.), making it a near-tautology.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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 the sibling 'get_executions' tool, or what prerequisites (active connection, selected account) might be required. No alternatives or exclusions mentioned.

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