Skip to main content
Glama

check_pro_institutional_bridge

Checks localhost readiness for institutional Level-2 and execution bridges (Moomoo OpenD, IB Gateway/TWS, MetaTrader 5) and displays Pro upgrade details.

Instructions

Check localhost (127.0.0.1) readiness for institutional Level-2 / execution bridges (Moomoo OpenD :11111 NASDAQ TotalView 60-depth, Interactive Brokers Gateway/TWS :4002/:7497, and MetaTrader 5 RPyC Bridge :8001) and display Lumina OrderBook MCP Pro upgrade details.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_pro_institutional_bridge"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden; it does disclose that the scope is strictly localhost/127.0.0.1 and enumerates the exact ports and providers probed. However, it does not state whether live TCP connections are attempted, what timeouts apply, or that one output branch is promotional content ("upgrade details") rather than diagnostics — an agent could be surprised by that.

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?

A single sentence with the action and full target list front-loaded, and every port/host detail earns its place for a connectivity probe. The trailing clause about upgrade details is tangential but brief rather than wasteful.

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?

For a zero-parameter diagnostic with an output schema available, the description covers scope, targets, and ports, which is most of what an agent needs. The remaining gap is failure/unreachable semantics, which is a modest omission given the output schema carries result structure.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description usefully clarifies that all targets are fixed and implicit rather than caller-supplied, which prevents an agent from searching for a host or port argument.

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?

The verb+resource pair is specific: check localhost readiness for named bridges (Moomoo OpenD :11111, IB Gateway/TWS :4002/:7497, MT5 RPyC :8001). The sibling names suggest adjacent tools deal with live data, and this one reads as a pre-flight connectivity probe, so it is distinguishable. It loses a point because it bundles a second, unrelated purpose ("display Lumina OrderBook MCP Pro upgrade details") into the same tool.

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?

Usage is only implied — an agent can infer this is a prerequisite check before calling live Level-2 tools like get_live_l2_orderbook, but the description never says so. There are no explicit when-to-use/when-not-to-use statements and no mention of what to do if a bridge is unreachable.

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