Amaltash Investment & Retirement Calculators

Stock Market Crash Calculator

crash_impact

Read-onlyIdempotent

Portfolio stress test with an interactive chart. Works out how much a portfolio would lose if stocks fell by a chosen percent, given its mix of stocks, bonds and cash, with an optional loss limit.

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": {
      "portfolio_value": "<portfolio_value>",
      "stocks_pct": "<stocks_pct>",
      "bonds_pct": "<bonds_pct>",
      "cash_pct": "<cash_pct>",
      "stock_crash_pct": "<stock_crash_pct>"
    },
    "name": "crash_impact"
  }
}

Input Schema

Name	Required	Description
`cash_pct`	Yes	Share of the portfolio in cash, in percent.
`bonds_pct`	Yes	Share of the portfolio in bonds, in percent.
`stocks_pct`	Yes	Share of the portfolio in stocks, in percent. Stocks, bonds and cash must add up to 100.
`portfolio_value`	Yes	Total portfolio value in US dollars.
`stock_crash_pct`	Yes	How far stocks fall, in percent, from 0 to 100.
`drawdown_limit_pct`	No	Optional limit on the portfolio loss, in percent of the portfolio. Leave null for no limit.

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 safety and side-effect behaviour is fully covered. The description adds that output includes an interactive chart and that a loss limit is optional, but does not explain what happens when the limit is breached (capped result versus error) or how the result is presented numerically.

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 scenario and then the mechanics, with no filler. The trailing 'with an interactive chart' is slightly decorative where a clearer statement of the output would earn more, but nothing is wasted.

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?

For a six-parameter pure calculator with full schema documentation and annotations covering side-effect profile, the description is nearly sufficient. Its only material gap is not describing what a result looks like or how the optional loss limit alters the answer, which matters a little 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 description coverage is 100%, so every parameter including the cash/bonds/stocks split and drawdown_limit_pct is already documented in the schema, giving a baseline of 3. The description restates those concepts in prose ('mix of stocks, bonds and cash', 'optional loss limit') without adding units, edge-case behaviour or the sum-to-100 constraint that the schema supplies.

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 computation: how much a portfolio loses when stocks fall by a given percent, weighted by its stocks/bonds/cash mix. That is clearly distinguishable from sibling calculators like drawdown_recovery or sequence_risk, though no sibling is named 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 implied by the framing ('if stocks fell by a chosen percent'), making it obvious this is a hypothetical stress test rather than a historical replay. However, there is no explicit when-to-use statement, no exclusion of near-neighbours such as drawdown_recovery, and no note that the asset percentages must sum to 100 in the prose.

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?