Skip to main content
Glama

U.S. Market Regime

calculate_prop_firm_drawdown

Read-onlyIdempotent

Calculate deterministic prop-firm drawdown survival math: remaining trailing buffer, max consecutive losses before daily or trailing breach, and recommended buffer-anchored 1R dollar and contract caps.

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": "calculate_prop_firm_drawdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_sizeNoNominal evaluation or funded account balance in USD (default 50000).
point_value_usdNoDollar value per point per contract (default 20 for NQ; use 2 for MNQ, 50 for ES, 5 for MES).
daily_loss_limitNoMaximum single-day loss limit in USD (default 1000).
consecutive_lossesNoLosing streak length to stress-test (default 3).
risk_per_trade_usdNoPlanned dollar risk per trade (1R). Overrides planned_stop_points if provided.
planned_stop_pointsNoOptional stop distance in index points (e.g., 10 points on NQ/MNQ).
current_drawdown_usedNoDrawdown already consumed in USD (default 0).
max_trailing_drawdownNoMaximum trailing or static drawdown allowance in USD (default 2000).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish the safety profile (readOnlyHint, idempotentHint, openWorldHint=false, non-destructive), so the description is free to spend its words on behavior. It adds genuine value by disclosing what the math returns and that the results are deterministic and buffer-anchored, which tells the agent the output is a recommendation rather than a live account query. It stops short of disclosing assumptions such as how a 'breach' is determined or whether results are rounded, so a 4 rather than 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with the verb first, the domain second, and the three returned quantities last. No filler, no repetition of the title, and the most decision-relevant content leads.

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?

With eight optional parameters, no output schema, and only annotations covering the read-only profile, the description must convey what comes back — and it does list the three computed results. What is missing is the interpretive layer an agent would need to act on results: whether caps are per-contract or total, and what happens when current_drawdown_used already exceeds max_trailing_drawdown.

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% and every parameter carries a default and, for point_value_usd, concrete instrument values (NQ 20, MNQ 2, ES 50, MES 5), so the schema does the heavy lifting. The description adds only that risk_per_trade_usd is '1R' and that caps are 'buffer-anchored'; it does not restate or clarify the override relationship or the daily-vs-trailing limit distinction beyond what the schema already says.

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?

Uses a specific verb ('Calculate') plus a precisely scoped resource ('prop-firm drawdown survival math') and then enumerates the three concrete outputs: remaining trailing buffer, max consecutive losses before daily/trailing breach, and buffer-anchored 1R dollar and contract caps. An agent knows exactly what computation this performs, and the sibling tools (market regime, blind-chart drill) are unrelated enough that no disambiguation is needed.

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: 'survival math' and 'buffer-anchored 1R' suggest pre-trade position sizing and risk stress-testing, but the description never states when to call it, what preconditions exist (e.g., account in evaluation vs funded), or when not to use it. No alternatives are named, though the siblings are not plausible substitutes.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.