Skip to main content
Glama
Universal Quant Tournament MCP

Universal Quant Tournament MCP

build_universal_bracket_order

Build risk-sized, leverage-aware bracket order payloads for Alpaca, MetaTrader 5, and Tradovate/TradingView webhooks, converting entry, stop-loss, and take-profit levels into broker-ready JSON.

Instructions

Generates risk-sized, leverage-aware bracket order payloads for Alpaca (Equities/Crypto), MetaTrader 5 (Forex/CFD/Metals with 100 oz Gold lot sizing and USD/JPY cross-rate conversion), and Tradovate/TradingView Webhooks (Futures).

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": {
      "symbol": "<symbol>",
      "bias": "<bias>",
      "entry_price": "<entry_price>",
      "stop_loss": "<stop_loss>",
      "take_profit": "<take_profit>"
    },
    "name": "build_universal_bracket_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
biasYesTrade direction.
symbolYesAsset ticker (e.g., 'XAU/USD', 'GBP/JPY', 'NVDA', 'MNQ').
stop_lossYesPlanned stop-loss price.
asset_classNoTarget asset class for lot/share/contract math.EQUITY
entry_priceYesPlanned entry price.
take_profitYesPlanned take-profit price.
broker_formatNoTarget broker payload schema.universal
account_leverageNoAccount leverage ratio (e.g., 1, 4, 20, 50, 100).
account_equity_usdNoTotal account equity in USD.
risk_per_trade_pctNoFraction of account equity to risk (0.02 = 2%).
contract_multiplierNoPoint value multiplier for Futures (e.g., 2 for MNQ, 20 for NQ).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. 'Generates payloads' usefully implies no order is actually transmitted, and the MT5 clause discloses concrete conversion behavior (100 oz gold lot sizing, USD/JPY cross-rate). However it omits error behavior (e.g., what happens on an asset_class/broker_format mismatch), whether prices are fetched live or taken purely from inputs, and whether any external side effect exists.

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?

One front-loaded sentence with the core action first and the broker qualifications following; no filler. It is dense — the parenthetical nesting around MT5 details is heavy — but each clause conveys usable information.

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?

This is an 11-parameter generation tool with no annotations and no output schema, so the description is the only place to learn what comes back — yet it says nothing about the shape of the returned payload (single object? per-broker schema? fields?), which is the whole point of the tool. It also doesn't reconcile the two correlated enums (asset_class vs broker_format) that determine which math path runs.

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 100%, so all 11 parameters are already documented with types, ranges, defaults and enums; the baseline of 3 applies. The description adds only the conceptual framing ('risk-sized' → risk_per_trade_pct/account_equity_usd, 'leverage-aware' → account_leverage) without any per-parameter syntax or interaction detail beyond the schema.

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?

States a specific verb+resource pair ('Generates ... bracket order payloads') with the qualifying traits 'risk-sized' and 'leverage-aware', plus the three broker targets. The word 'payloads' implicitly separates it from execution-oriented siblings like sync_or_execute_local_mt5, but that contrast is never stated outright.

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 broker list hints at the applicable domain (Alpaca, MT5, Tradovate/TradingView), but there is no explicit when-to-use, when-not-to-use, or named alternative. In particular, it never says 'this only builds the order and does not submit it — use the execution tool to place it', which is exactly the routing decision an agent must make against sync_or_execute_local_mt5.

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