Skip to main content
Glama
Universal Quant Tournament MCP

Universal Quant Tournament MCP

run_monte_carlo_stress_test

Simulate 1,000 Bayesian Monte Carlo paths and Half-Kelly risk to stress-test entry, stop-loss, and take-profit, then gate strategy execution by probability of profit.

Instructions

Runs a 1,000-path Bayesian Out-of-Sample Monte Carlo simulation and Half-Kelly risk assessment on a strategy's entry, stop-loss, take-profit, and validated win rate.

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

Input Schema

NameRequiredDescriptionDefault
stop_lossYesPlanned stop-loss price.
entry_priceYesPlanned entry price.
take_profitYesPlanned take-profit price.
slippage_bpsNoEstimated execution slippage in basis points (default: 5).
win_rate_priorNoValidated win rate from the tournament champion.
simulation_pathsNoNumber of Monte Carlo paths to simulate (default: 1000).
risk_per_trade_pctNoFraction of account equity risked per trade (0.02 = 2%).
min_probability_of_profit_pctNoMinimum required probability of profit percentage (e.g., 65, 75, 90) to approve execution.

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?

No annotations were supplied, so the description carries the full burden. It does disclose meaningful method (Bayesian out-of-sample sampling, Half-Kelly sizing, 1,000 paths), which suggests a computed, non-mutating analysis. However, it never says whether the call is read-only, whether it gates or approves execution, whether it requires a validated tournament champion as a precondition, or what the result looks like — significant omissions for a risk-gating tool with zero annotation coverage.

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 no filler or repetition. It is dense but every clause carries information, and the method qualifiers are packed efficiently.

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?

With eight parameters, no output schema and no annotations, the description should explain what comes back — probability of profit, Kelly fraction, pass/fail against min_probability_of_profit_pct. It says nothing about return values or the approval gate that one of its own parameters implies, leaving a real gap for a decision-producing tool.

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 eight parameters are already documented with types, bounds and defaults, making 3 the baseline. The description echoes the simulation path count and names the four core inputs, but adds no new semantics such as how slippage interacts with the simulation or how the win-rate prior is consumed.

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 description uses a specific verb ("Runs") on clearly named resources: a 1,000-path Bayesian Out-of-Sample Monte Carlo simulation plus a Half-Kelly risk assessment, over entry, stop-loss, take-profit and win rate. That is far more specific than the sibling names (tournament, bracket order, MT5 sync) and lets an agent tell it apart. It stops short of stating the tool's outcome (an approval/gating decision), which keeps it off a 5.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. Pre-trade usage is only faintly implied by "on a strategy's entry, stop-loss, take-profit, and validated win rate"; nothing tells the agent whether this should be run before build_universal_bracket_order or instead of run_multi_strategy_tournament.

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