mm-ibkr-mcp

Overview Schema Source Related Servers Discussions Admin

Check Position Limits

check_position_limits

Read-onlyIdempotent

Validate a proposed order against the active agent profile's position limits to prevent violations. Returns passed=true when compliant.

Instructions

Validate a proposed order against the active agent profile's position limits. Returns passed=true when no violations are found.

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": {
      "order": "<order>"
    },
    "name": "check_position_limits"
  }
}

Input Schema

Name	Required	Description	Default
`order`	Yes
`account_id`	No
`profile_id`	No

Output Schema

Name	Required	Description
`passed`	Yes	True if all limit checks passed.
`profileId`	Yes	Profile used for the check.
`violations`	No	List of violated limits.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 8, 2026

TDQS

B3.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description does not contradict them. It adds the behavioral detail that the tool returns a boolean 'passed' value, which is informative. However, it does not elaborate on side effects (likely none) or error behaviors, but given annotations cover safety profile, this is adequate.

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 concise, consisting of two sentences with no redundant wording. It directly states the purpose and the expected outcome, making it efficient and easy to parse for an agent.

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?

Despite the complexity of the input schema (with a detailed OrderSpec and SymbolSpec), the description only offers a high-level overview. It does not clarify how account_id and profile_id interact with the order, what 'position limits' encompass, or how the validation result should be interpreted by the caller. The output schema exists but the input context remains underexplained for a tool of this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the three top-level parameters (order, account_id, profile_id), and the description provides no explanation of these parameters or their roles. The only inferred parameter is the 'proposed order' mentioned in the description, but account_id and profile_id are entirely unaddressed, leaving the agent without necessary semantic understanding.

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: validating a proposed order against position limits, and explicitly defines the return value (passed=true when no violations). It uses a specific verb ('validate') and specifies the resource ('active agent profile's position limits'), making the purpose unambiguous even among sibling tools.

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?

The description does not provide any guidance on when to use this tool versus alternatives like validate_against_profile, check_approval_status, or assess_order_impact. It implicitly suggests use during order validation but lacks explicit direction, leaving the agent to infer the appropriate context without contrasting sibling tools.

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