Skip to main content
Glama

crashtestyourstrategy

Long-horizon wealth-path stress (savings / withdrawal plans)

long_horizon_stress
Read-onlyIdempotent

USE WHEN you want multi-year wealth paths for a savings plan or a withdrawal plan. Distribution of multi-year wealth paths for a savings plan (monthly_contribution) or a withdrawal plan (monthly_withdrawal, inflation-indexed by default) on a SPY/TLT/GOLD/BTC portfolio. Multi-year paths chain ~2y model blocks (block-bootstrap); long-run drift is RE-ANCHORED to stated round-number assumptions (overridable via long_run_drift; see assumptions.long_run_drift) while the model's path shape is kept; both are echoed. Costs are ON by default. Returns terminal-wealth quantiles (nominal + real), ruin/shortfall probabilities, a sequence-of-returns diagnosis and a drift sensitivity (assumptions - 2pp). Descriptive, not advisory; no rate, allocation or product is recommended.

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": {
      "holdings": "<holdings>",
      "horizon_years": "<horizon_years>"
    },
    "name": "long_horizon_stress"
  }
}

Input Schema

NameRequiredDescriptionDefault
holdingsYesPortfolio legs: list of {asset, weight} objects, e.g. [{'asset': 'SPY', 'weight': 0.6}, {'asset': 'TLT', 'weight': 0.4}]. Assets: SPY, TLT, GOLD, BTC (aliases GLD, BTC-USD). Weights are non-negative and normalised to sum to 1; at most 50 legs, no duplicates.
rebalanceNoRebalancing frequency: 'daily' | 'monthly' | 'quarterly'.monthly
horizon_yearsYesPlan horizon in years (multi-year paths are chained from ~2-year model blocks).
target_amountNoOptional wealth target; the output reports the probability of reaching it.
long_run_driftNoOverride the re-anchored long-run drift per asset: {ASSET: annual drift fraction}; omit for the stated round-number assumptions (assumptions.long_run_drift in the response).
annual_inflationNoAnnual inflation assumption for indexing and real-value reporting (fraction, default 0.02).
initial_investmentNoStarting capital (account currency).
monthly_withdrawalNoMonthly withdrawal (withdrawal-plan mode); inflation-indexed when withdrawal_inflation_indexed is true.
monthly_contributionNoFixed monthly savings contribution (savings-plan mode).
withdrawal_inflation_indexedNoIndex the monthly withdrawal to inflation.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / long_run_drift / description
      Previous value: -"Override the re-anchored long-run drift per asset: {ASSET: annual drift fraction}; omit for the stated capital-market assumptions."New value: +"Override the re-anchored long-run drift per asset: {ASSET: annual drift fraction}; omit for the stated round-number assumptions (assumptions.long_run_drift in the response)."
  2. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / holdings / description
      Previous value: -"Portfolio legs: list of {asset, weight} objects, e.g. [{'asset': 'SPY', 'weight': 0.6}, {'asset': 'TLT', 'weight': 0.4}]. Weights are normalised to sum to 1; assets must be in the substrate universe."New value: +"Portfolio legs: list of {asset, weight} objects, e.g. [{'asset': 'SPY', 'weight': 0.6}, {'asset': 'TLT', 'weight': 0.4}]. Assets: SPY, TLT, GOLD, BTC (aliases GLD, BTC-USD). Weights are non-negative and normalised to sum to 1; at most 50 legs, no duplicates."
  3. Changed10 schema fields changed
    • addedInput schema / properties / annual_inflation / description
      Added value: +"Annual inflation assumption for indexing and real-value reporting (fraction, default 0.02)."
    • addedInput schema / properties / holdings / description
      Added value: +"Portfolio legs: list of {asset, weight} objects, e.g. [{'asset': 'SPY', 'weight': 0.6}, {'asset': 'TLT', 'weight': 0.4}]. Weights are normalised to sum to 1; assets must be in the substrate universe."
    • addedInput schema / properties / horizon_years / description
      Added value: +"Plan horizon in years (multi-year paths are chained from ~2-year model blocks)."
    • addedInput schema / properties / initial_investment / description
      Added value: +"Starting capital (account currency)."
    • addedInput schema / properties / long_run_drift / description
      Added value: +"Override the re-anchored long-run drift per asset: {ASSET: annual drift fraction}; omit for the stated capital-market assumptions."
    • addedInput schema / properties / monthly_contribution / description
      Added value: +"Fixed monthly savings contribution (savings-plan mode)."
    • addedInput schema / properties / monthly_withdrawal / description
      Added value: +"Monthly withdrawal (withdrawal-plan mode); inflation-indexed when withdrawal_inflation_indexed is true."
    • addedInput schema / properties / rebalance / description
      Added value: +"Rebalancing frequency: 'daily' | 'monthly' | 'quarterly'."
    • addedInput schema / properties / target_amount / description
      Added value: +"Optional wealth target; the output reports the probability of reaching it."
    • addedInput schema / properties / withdrawal_inflation_indexed / description
      Added value: +"Index the monthly withdrawal to inflation."
  4. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare a safe, idempotent, closed-world read, and the description still adds substantial behavioral context: paths are chained from ~2-year blocks, long-run drift is re-anchored to round-number assumptions and echoed in the response, costs are ON by default, and a drift sensitivity of assumptions minus 2pp is reported. The 'descriptive, not advisory' scope note is a useful framing constraint beyond anything in the annotations.

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?

The trigger clause is front-loaded and every clause carries content, including defaults and output shape. It is dense, with heavy parenthetical nesting (assumptions - 2pp, assumptions.long_run_drift), which slows scanning slightly but does not waste sentences.

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 10-parameter simulation tool with an output schema and full annotation coverage, the description supplies mode selection, cost defaults, drift handling, inflation behavior, and the nature of reported results. The remaining gap is operational: no guidance on what horizon_years range is supported or how expensive a long-horizon run is, which matters for a chained-block simulation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline would be 3, but the description adds meaning the schema does not: monthly_contribution selects savings mode, monthly_withdrawal selects withdrawal mode and is inflation-indexed by default, and long_run_drift overrides values echoed in assumptions.long_run_drift. That mode-selection mapping is the key semantic addition. It still does not explain interactions such as how horizon_years interacts with the ~2-year block chaining beyond a parenthetical.

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?

Names a specific capability: multi-year wealth-path distributions for savings or withdrawal plans on a SPY/TLT/GOLD/BTC portfolio, with chained block-bootstrap blocks and re-anchored drift. An agent can tell exactly what it produces. What's missing is explicit differentiation from the similarly named siblings (portfolio_stress_test, run_stress_test, tier2_stress_test), which share vocabulary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Opens with an explicit 'USE WHEN you want multi-year wealth paths for a savings plan or a withdrawal plan', which is a real trigger condition. It also implicitly encodes mode selection through monthly_contribution vs monthly_withdrawal. However, it never states when NOT to use it or which sibling to prefer for single-period or portfolio-level stress tests.

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.