Skip to main content
Glama
nadavgb-atom

ib-async-mcp

by nadavgb-atom
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

disconnect

Terminate the connection to Interactive Brokers TWS or IB Gateway, ending all active data streams and trading sessions.

Instructions

Disconnect from TWS/Gateway.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/ib_async_mcp/server.py:462-466 (handler)
    The handler logic for the 'disconnect' tool, which sets the 'ib' client to None and calls its disconnect method.
    if name == "disconnect":
    if ib is not None:
        ib.disconnect()
        ib = None
    return {"status": "disconnected"}
  • src/ib_async_mcp/server.py:80-84 (registration)
    Registration of the 'disconnect' tool with name, description, and empty input schema.
    Tool(
    name="disconnect",
    description="Disconnect from TWS/Gateway.",
    inputSchema={"type": "object", "properties": {}},
),

Tool Definition Quality

B3.1/5.0
Behavior2/5

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

No annotations provided, leaving full burden to description. Fails to disclose whether disconnect is graceful, requires authentication cleanup, affects pending operations, or what happens if called when already disconnected.

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?

Extremely brief single sentence. Efficient for a parameterless operation, though brevity is excessive given lack of annotations and behavioral context that should have been included.

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?

Adequate for identifying the operation but insufficient given the stateful nature implied by siblings (connect/is_connected). Missing prerequisite warnings and effect descriptions that would complete the definition.

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?

Zero parameters present; baseline score of 4 applies per evaluation rules. Schema coverage is vacuously 100% with empty properties object.

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

Purpose4/5

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

Clear specific verb (Disconnect) and target resource (TWS/Gateway). Implicitly distinguishes from sibling 'connect' by describing opposite action, though explicit comparison would strengthen it.

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?

No guidance provided on when to use versus 'is_connected' check, prerequisites (requires active connection), or cleanup behavior (e.g., handling open orders before disconnect).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nadavgb-atom/ib-async-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server