Skip to main content
Glama
Sign In
Interactive Brokers MCP Server

Interactive Brokers MCP Server

by code-rabi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_alerts

Retrieve all trading alerts for your Interactive Brokers account by providing your account ID.

Instructions

Get all trading alerts for an account. Usage: { "accountId": "<id>" }.

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": {
      "accountId": "<accountId>"
    },
    "name": "get_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.21.3
  2. Removedv1.15.1
  3. Addedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states that alerts are retrieved, with no mention of side effects, authentication requirements, rate limits, or behavior details. For a read operation, this is minimal.

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

Conciseness4/5

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

The description is very short and front-loaded with the purpose. The usage example is clearly formatted. However, it could include more context without being overly verbose.

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 and no annotations, the description lacks completeness. It doesn't describe return values, error conditions, or pagination. For a simple parameter tool, some additional context is expected.

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

Parameters2/5

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

The schema has 0% description coverage, and the description only gives a usage example for accountId without explaining what it represents, its format, or constraints. This adds minimal meaning beyond the schema.

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 uses a specific verb ('Get') and resource ('trading alerts'), clearly stating what the tool does and distinguishing it from sibling tools like create_alert or delete_alert.

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 provides a usage example but offers no guidance on when to use this tool versus alternatives like get_account_info or get_live_orders. No when-not-to-use context is given.

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