mm-ibkr-mcp

Overview Schema Source Related Servers Discussions Admin

Get Session Activity

get_session_activity

Read-onlyIdempotent

Summarize today's trading session by reviewing orders placed, filled, cancelled, or pending, including the most recent order details.

Instructions

Summarise trading activity for today's session: orders placed, filled, cancelled, and pending — with a list of the most recent orders.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_session_activity"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`sessionDate`	Yes	Session date (UTC, YYYY-MM-DD).
`ordersFilled`	Yes	Orders filled in this session.
`ordersPlaced`	Yes	Orders placed in this session.
`recentOrders`	No	Most recent orders (up to 20).
`ordersPending`	Yes	Orders still open.
`ordersCancelled`	Yes	Orders cancelled in this session.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 8, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The annotations already declare readOnlyHint and idempotentHint, and the description aligns with a safe, read-only summarization behavior. It adds useful context about session scope and recent orders but does not elaborate on data freshness or potential variations.

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

Conciseness5/5

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

The description is a single, focused sentence with no redundant wording. It efficiently conveys what the tool does and what it returns.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description adequately explains the tool's output categories and the inclusion of recent orders. However, it does not define 'today's session' boundaries or timezone, which could be mildly ambiguous in a trading context.

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?

There are no parameters in the schema, so the description does not need to explain parameter behavior. The baseline for zero parameters is appropriate here.

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

Purpose5/5

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

The description clearly states the tool's purpose with a specific verb ('Summarise') and resource ('trading activity for today's session'), including the categories of orders and a list of recent orders. It distinguishes itself from related order and account tools.

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for getting a session-level summary of trading activity, but it does not explicitly state when to use this tool versus alternatives like list_open_orders, get_order_status, or get_pnl.

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