Amaltash Investment & Retirement Calculators

Loss Recovery Calculator

drawdown_recovery

Read-onlyIdempotent

Drawdown and loss recovery calculator with an interactive chart. Works out the percentage gain needed to get back to even after a loss, and how many years that takes at a yearly return the person enters.

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_pct": "<loss_pct>"
    },
    "name": "drawdown_recovery"
  }
}

Input Schema

Name	Required	Description	Default
`loss_pct`	Yes	The loss, in percent, from 0 up to but not including 100.
`annual_return_pct`	No	Optional yearly return, in percent, used to estimate years to recover. Leave null to skip the estimate.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds computational semantics (breakeven gain, time-to-recover) but the phrase 'with an interactive chart' is ambiguous and no return shape is described, which matters because there is no output schema.

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?

Two sentences, front-loaded with the tool's identity and followed by the actual computation. The only questionable element is the 'interactive chart' clause, which does not obviously map to any parameter or documented output.

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?

This is a simple two-parameter calculation tool with full schema coverage and complete safety annotations, and the description explains what is computed. The remaining gap is that it never says what the caller receives back, which is a moderate omission given there is no output schema.

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%, so both loss_pct and annual_return_pct are already documented with bounds and nullability. The description echoes the meaning of each ('a loss', 'a yearly return the person enters') but adds no format, unit, or edge-case 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?

The description names a specific resource and computation: the percentage gain needed to return to breakeven after a loss, plus the years required at a user-supplied annual return. It is clearly distinguished from return-generating siblings like compound_interest or dca_vs_lump_sum, though it never names an alternative explicitly.

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 by the phrase 'after a loss' and by the mention of an optional yearly return. There is no statement of when to prefer this over related calculators, no preconditions, and no exclusions.

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

All Amaltash Investment & Retirement Calculators tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?