Skip to main content
Glama
Universal Quant Tournament MCP

Universal Quant Tournament MCP

sync_or_execute_local_mt5

Pull live MetaTrader 5 OHLCV candles and account equity/leverage, or execute an approved bracket order only after explicit user confirmation.

Instructions

Connects directly to the user's open Windows MetaTrader 5 desktop terminal to either (1) pull live broker OHLCV candles and account equity/leverage, or (2) execute an approved mt5_mql5_order_send bracket order after explicit user confirmation.

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": {
      "action": "<action>"
    },
    "name": "sync_or_execute_local_mt5"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesUse 'fetch_bars' to read live candles/account info, or 'execute_order' to fire an approved order.
symbolNoMT5 symbol (e.g., 'XAUUSD', 'GBPJPY', 'EURUSD').GBPJPY
timeframeNoCandle timeframe when action is 'fetch_bars'.15Min
lookback_barsNoNumber of MT5 bars to pull when action is 'fetch_bars'.
mt5_order_payloadNoThe mt5_mql5_order_send object generated by build_universal_bracket_order.
user_confirmed_executionNoMUST be true to execute an order. Only set to true after explicit user confirmation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.8/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 load, and it does disclose key context: this requires a running Windows MT5 desktop terminal, and order execution is gated on explicit user confirmation of an already-approved bracket. What is missing is the downside profile — that execute_order places a real, irreversible live trade, what happens on connection failure or rejection, and whether fetch_bars side effects are truly read-only. Adequate but notably incomplete for a tool with a live-money mutation path.

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 front-loaded sentence with the resource and environment stated first, then the two modes enumerated as (1) and (2) — no filler and no repetition of schema fields. The nested parenthetical makes it slightly dense to parse, but every clause earns its place.

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?

For a six-parameter, nested-payload, no-annotation tool, the description covers the two modes and hints at what fetch_bars returns (candles, equity, leverage), which partially compensates for the absent output schema. It omits failure/error behavior, whether execute_order returns a ticket or fill status, and any rate/timeout expectations for a long-lived desktop connection — meaningful gaps given the live-trading stakes.

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 coverage is 100%, including per-parameter descriptions, enums, defaults, and the nested order payload, so the schema already does the semantic work and the baseline is 3. The description adds only the cross-tool provenance of the payload (that it comes from build_universal_bracket_order) and does not clarify symbol conventions, lookback/latency tradeoffs, or what the confirmation flag changes in behavior beyond restating 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 names a specific verb and resource ('Connects directly to the user's open Windows MetaTrader 5 desktop terminal') and then enumerates the two distinct operations: pulling live broker OHLCV candles plus account equity/leverage, or executing an approved bracket order. It also ties itself to the sibling pipeline by naming build_universal_bracket_order as the source of the order payload, so an agent can distinguish it from the tournament/stress-test siblings without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Each numbered branch maps to a clear situation: read live market/account data versus fire an order that is already approved and explicitly confirmed by the user. The prerequisite (an order built by build_universal_bracket_order, plus explicit confirmation) is stated, which is meaningful routing guidance. It stops short of explicit exclusions — e.g. it never says what to use instead when the terminal is unavailable or when no order has been vetted.

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