Skip to main content
Glama
Sign In
Interactive Brokers MCP Server

Interactive Brokers MCP Server

by code-rabi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

authenticate

Authenticate with Interactive Brokers by sending a confirmation request to establish a secure connection for trading.

Instructions

Authenticate with Interactive Brokers. Usage: { "confirm": true }.

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": {
      "confirm": "<confirm>"
    },
    "name": "authenticate"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.21.3
  2. Removedv1.15.1
  3. Changed3 schema fields changedv1.0.0
    • addedInput schema / properties / confirm
      Added value: +{
+  "const": true,
+  "type": "boolean"
+}
    • removedInput schema / properties / random_string
      Removed value: -{
-  "description": "Dummy parameter for no-parameter tools",
-  "type": "string"
-}
    • addedInput schema / required
      Added value: +[
+  "confirm"
+]
  4. First observed

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behaviors. It only states 'Authenticate' and gives a usage example, omitting what happens upon success (e.g., session token), error states, or side effects. This is insufficient for understanding the tool's full impact.

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 extremely concise with two short sentences. No extraneous information is included. Every element (action, target, usage example) serves a clear purpose.

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

Completeness3/5

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

Given the tool's low complexity (single parameter, no output schema), the description provides the essential action and parameter usage. However, it lacks details on return values or post-authentication state, which would be helpful for an authentication tool. It is minimally adequate.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must compensate. It does so partially by providing a usage example (`{"confirm": true}`) that clarifies the parameter's purpose as a confirmation flag. However, it does not explain why confirmation is required or what it safeguards against.

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 explicitly states the tool's action ('Authenticate') and target ('Interactive Brokers'). This is a specific verb+resource combination that distinguishes it from sibling tools like 'activate_alert' or 'place_order'.

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 initial authentication but provides no explicit guidance on when to use versus alternatives (e.g., re-authentication). No exclusion conditions or prerequisites are mentioned.

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