Skip to main content
Glama

Drawdown recovery calculator

calculate_drawdown_recovery
Read-onlyIdempotent

The gain needed to recover from a drawdown and, optionally, how many losing trades in a row at a fixed risk per trade cause it. Computed with the same function as Clear Tape's free drawdown recovery calculator page (linked in the result), not estimated. Returns the inputs, each result with its unit, the formula and the page link. Educational, not investment advice.

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": {
      "loss": "<loss>"
    },
    "name": "calculate_drawdown_recovery"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the returned text: "en" (default) or "zh" (Simplified Chinese).en
lossYesDrawdown in percent of the account (20 = 20%). Above 0, below 100.
riskPctNoOptional: risk per trade in percent of the account. Above 0, below 100.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive profile, and the description adds real value on top: it is a deterministic computation from the same function as the linked public page rather than an estimate, and it discloses the return contents (inputs, results with units, formula, page link). The educational disclaimer is also useful context.

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?

Three compact sentences, front-loaded with the primary result and the optional one, with no filler. Slightly dense in the first sentence but every clause carries information.

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 no output schema, the description compensates by naming what comes back (inputs, results with units, formula, page link) and by flagging the optional riskPct behavior. Only the input-validation story (loss must be between 0 and 100) is left entirely to the schema, which is acceptable given the 100% coverage.

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 loss, riskPct and lang are fully documented with bounds and defaults at baseline 3. The description restates the drawdown and fixed-risk-per-trade concepts but adds no syntax or semantics 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 concrete computation: the gain needed to recover from a drawdown, plus optionally the consecutive-losing-trade count at a fixed risk. Verb and resource are specific, though the optional losing-streak output overlaps conceptually with the sibling calculate_losing_streak and the description does not address that boundary.

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: supplying riskPct triggers the losing-streak result, otherwise only the recovery gain is returned. There is no when-to-use/when-not guidance and no routing to or away from the sibling calculators, so an agent must infer the context.

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.

Resources