Skip to main content
Glama
nadavgb-atom

ib-async-mcp

by nadavgb-atom

get_executions

Retrieve execution reports from Interactive Brokers to monitor trade confirmations and transaction details for account management.

Instructions

Get execution reports.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler logic for "get_executions" which fetches executions from the IB connection and serializes them.
    if name == "get_executions":
        executions = ib.executions()
        return [serialize_object(e) for e in executions]
  • Registration of the "get_executions" tool within the MCP server definition.
    Tool(
        name="get_executions",
        description="Get execution reports.",
        inputSchema={"type": "object", "properties": {}},
    ),
Behavior2/5

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

No annotations are provided, yet the description fails to disclose what data the reports contain, whether results are paginated, time-range limited, or the format of returned execution data. Does not mention if this requires authentication or specific account permissions.

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?

While brief at only three words, it is under-specified rather than efficiently informative. Lacks front-loaded critical constraints or scoping details that would help an agent determine if this tool fits their need.

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?

Given the complex financial trading domain evidenced by siblings (orders, positions, PnL), the description is insufficient. It does not indicate what time period is covered, what fields are returned, or how this relates to account history.

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 has zero parameters, establishing baseline 4. Description neither adds nor removes value regarding parameters since none exist to document.

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 a verb ('Get') and resource ('execution reports'), but 'execution' is vague in this trading context and fails to distinguish from sibling tool 'get_fills' or indicate what constitutes an execution versus a fill or trade.

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 tool versus alternatives like 'get_fills' or 'get_open_trades', nor mentions prerequisites such as requiring an active connection (implied by sibling 'connect'/'is_connected' tools).

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