Skip to main content
Glama
Sign In
ibkr-mcp

ibkr-mcp

by zionto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

flex_analyze_dividends

Summarize dividend income and withholding taxes from Interactive Brokers Flex XML, returning gross dividends, withheld tax, net dividends, and per-symbol details.

Instructions

Summarize dividend income and withholding taxes from cash transactions.

Args: xml_content: Raw Flex XML string.

Returns JSON with total gross dividends, total withholding tax, net dividends, and a per-symbol breakdown.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "xml_content": "<xml_content>"
    },
    "name": "flex_analyze_dividends"
  }
}

Input Schema

NameRequiredDescriptionDefault
xml_contentYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, the description carries full behavioral disclosure burden. It outlines the output structure (JSON with totals and breakdown), but does not disclose side effects (likely none since it's an analysis), error handling, or limitations. The output description adds some transparency beyond the schema.

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 exceptionally concise, with a clear one-line purpose, an annotated Args section, and a brief summary of return values. Every sentence earns its place with no filler or redundancy.

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 tool is simple (one parameter) and the description covers purpose, parameter meaning, and output structure. It does not mention error handling or prerequisites beyond raw Flex XML, but for an analysis tool of this scope, it is adequately complete.

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?

The schema description coverage is 0%, so the description must compensate. It explains 'xml_content' as 'Raw Flex XML string', providing meaning beyond the type 'string' in the schema. This is sufficient for a single parameter, though it lacks details like format or size constraints.

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 function with a specific verb ('Summarize') and resource ('dividend income and withholding taxes from cash transactions'). It effectively distinguishes itself from sibling parsing tools like flex_parse_cash_txns by focusing on dividend analysis.

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 context through 'from cash transactions' but does not explicitly state when to use this tool over alternatives or provide exclusions. No mention is made of sibling tools or use cases where this analysis is appropriate.

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

Deploy Server

Other Tools