FreeDailyPro Tools

converters_retirement

Read-onlyIdempotent

Retirement and FIRE projection: nest egg, sustainable income, gap and drawdown with inflation and a withdrawal rate

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": {
      "currentAge": "<currentAge>",
      "retirementAge": "<retirementAge>"
    },
    "name": "converters_retirement"
  }
}

Input Schema

Name	Required	Description
`currentAge`	Yes	Your age now (whole years).
`inflationPct`	No	Expected inflation, percent a year (default 2.5).
`retirementAge`	Yes	Age you plan to stop working.
`currentSavings`	No	Invested savings now.
`expectedReturnPct`	No	Expected nominal return before retirement, percent a year (default 7). An assumption, not market data.
`lifeExpectancyAge`	No	Age the money must last to (default 95).
`otherAnnualIncome`	No	Pension or Social Security per year in today's dollars, counted from the retirement age (default 0).
`withdrawalRatePct`	No	Share of the nest egg withdrawn in the first year (default 4).
`annualContribution`	No	What you add each year, in today's dollars.
`desiredAnnualIncome`	No	Income you want per year in today's dollars. Adds the nest egg needed, the gap, the extra saving needed and the years to financial independence.
`contributionGrowthPct`	No	Yearly real increase of the contribution in percent (default 0).
`returnInRetirementPct`	No	Expected nominal return during retirement (default: same as before retirement).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

B3.3/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 determinism are covered structurally. The description adds that this is a projection built on assumptions (inflation, withdrawal rate) and hints at the return values, but does not state that results are deterministic estimates rather than advice, nor how the two required inputs drive the calculation. Modest added value over annotations.

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 no filler; every term (nest egg, sustainable income, gap, drawdown, inflation, withdrawal rate) maps to an input or an output of the tool. Nothing could be cut without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 12 parameters, no output schema, and only 2 required inputs, the description should at minimum clarify that currentAge and retirementAge are the anchors and roughly what shape the result takes. It names the outputs but not their form, and leaves the sibling overlap with converters_fire unresolved. Adequate but with clear gaps for a calculator of this size.

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 definition with its default, so the schema does the heavy lifting. The description's mention of 'inflation' and 'a withdrawal rate' merely echoes two schema entries without adding units, interactions, or defaults beyond what is already documented. Baseline 3 applies.

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 the resource (retirement/FIRE projection) and enumerates the computed outputs: nest egg, sustainable income, gap, drawdown, plus the inflation and withdrawal-rate levers. That is far more specific than a tautology. However, it never distinguishes itself from the sibling converters_fire, which the word 'FIRE' explicitly overlaps with, so an agent cannot route between them from this text alone.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not guidance, no prerequisites, and no named alternative. The presence of closely related siblings (converters_fire, converters_401k, converters_rmd, converters_social_security) makes this omission costly — the description gives no signal about which one an agent should pick.

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

All FreeDailyPro Tools 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?