Skip to main content
Glama

FreeDailyPro Calculators

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

NameRequiredDescriptionDefault
currentAgeYesYour age now (whole years).
inflationPctNoExpected inflation, percent a year (default 2.5).
retirementAgeYesAge you plan to stop working.
currentSavingsNoInvested savings now.
expectedReturnPctNoExpected nominal return before retirement, percent a year (default 7). An assumption, not market data.
lifeExpectancyAgeNoAge the money must last to (default 95).
otherAnnualIncomeNoPension or Social Security per year in today's dollars, counted from the retirement age (default 0).
withdrawalRatePctNoShare of the nest egg withdrawn in the first year (default 4).
annualContributionNoWhat you add each year, in today's dollars.
desiredAnnualIncomeNoIncome 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.
contributionGrowthPctNoYearly real increase of the contribution in percent (default 0).
returnInRetirementPctNoExpected nominal return during retirement (default: same as before retirement).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered and this is clearly a pure calculation. The description adds that results are projections driven by inflation and a withdrawal rate, which usefully flags the modeled assumptions, but says nothing about how outputs are structured or what happens with missing optional inputs.

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?

A single compact clause that front-loads the tool's identity and then lists the computed outputs. There is no filler, though the fragment style reads more like a label than a sentence and leaves no room for guidance.

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 12-parameter calculator whose schema documents every input with defaults, the description plus schema gives an agent enough to call it correctly, and the enumerated outputs partially compensate for the absence of an output schema. The remaining gap is routing guidance against near-neighbors like converters_fire and how the returned figures are shaped.

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 each of the 12 parameters carries a clear definition including defaults, so the schema does the heavy lifting. The description only echoes two of them (inflation and withdrawal rate) and adds no syntax, units, or interaction details beyond what the schema states.

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 verb+resource ('Retirement and FIRE projection') and enumerates its outputs (nest egg, sustainable income, gap, drawdown), so an agent can tell roughly what it computes. It does not, however, distinguish itself from the sibling converters_fire, which plausibly covers overlapping territory.

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: the phrase 'Retirement and FIRE projection' signals a retirement-planning scenario, but there is no explicit when-to-use, when-not-to-use, or any pointer to an alternative such as converters_fire. An agent must infer the fit from the description alone.

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