Skip to main content
Glama

firenum retirement planner

Build a retirement plan

build_retirement_plan
Read-only

Use when someone asks when they can retire, if their money will last, their FIRE number (the planner shows when they'd reach it), or about Coast, Barista, Lean or Fat FIRE, and gave numbers (age, income, savings, spending, debts). Send what they gave, as said. Returns its answer and plan link.

Turns what someone has said about their money into firenum's answer and their plan in firenum's Fire Planner (FIRE: Financial Independence, Retire Early). The answer is the planner's own, as their plan shows it once opened: when they can retire with their contributions, growth and inflation, graded three ways (average returns, 500 Monte Carlo simulations, every historical start year since 1872). For a FIRE number it gives the number and, once it has their age, when they would reach it. All parameters are optional: with too little to grade, missing says what to ask for.

Reply from answer. Give the headline with both counts: the headline's date is the first month the money lasts on average returns, and the counts say how often that survives real market swings. When a count is under half, open with that count ("The money lasts in only N of 500 simulated markets"), never with yes, even a qualified one ("on average returns, yes", "a risky yes"): the date works on average but fails in most markets. coast_number is their Coast FIRE number for coast_age (what they would need invested today to stop saving). coast is the planner's own answer to stopping saving today: whether the money still lasts if they retire on the headline's date and, if not, the date that works without more saving. assumed, when present, is what the answer took for something they didn't say: say so in those terms. missing is what the planner needs before it can grade anything: ask for it and call again. To grade another retirement year, call again with retire. Amounts are in their currency, sums in today's money. table is their net worth year by year on each model, with income, spending and withdrawals, and assumptions is what the answer rests on (the rates, how each model works, how their numbers were read, what is not modeled): answer follow-ups from them (what they would have at 60, when the money runs out in a bad market, why a date) without calling again, and say what an answer assumes when it matters.

Give them the returned url exactly as it is: it opens their quick-start with these numbers filled in, then the whole plan (stress tests, a year-by-year table, where the money goes). Without source=agent the planner opens it as a shared plan that saves nothing. It runs in their browser with no account, and nothing is saved until they confirm: the link then becomes a new plan, "From a link", beside any plans they have. The plan keeps the accounts, spending lines, debts, pension, Social Security and rental income sent. Salary and side income become one monthly income.

Income is annual. Expenses and contributions are monthly. Amounts in whole currency units (not cents). Growth and inflation are percentages.

Taxes are off by default, in any country: income is take-home pay. For someone in the US who gives income before tax, send taxes=us (and state, a partner, dependents, their Social Security statement figure and a Roth conversion strategy when they say them): the planner then computes federal, state and payroll tax every year, and the table gains each year's tax. Amounts are then dollars.

Before retirement, any spending, debt payments and contributions that income doesn't cover are paid from savings. Without salary or side_income, and with retirement still ahead, the answer assumes an income that covers spending, contributions and debt payments until then (assumed says so), and the quick-start asks for it.

Input Schema

NameRequiredDescriptionDefault
hsaNoHealth Savings Account balance. Default growth 7%.
piaNoMonthly Social Security benefit at full retirement age, from the SSA statement. The planner computes the benefit for claim_age from it.
cashNoCash/checking balance. Default growth 0%.
debtNoDebt balance.
foodNoMonthly food expense.
rothNoRoth account balance (Roth IRA, Roth 401k). Default growth 7%.
birthNoBirth year (YYYY). From an age, send the current year minus the age. Used with retire_age to compute retirement date.
stateNoTwo-letter US state code (DC too) for state income tax. Without it, federal tax only.
taxesNo"us" computes US federal, state and payroll tax every year (2026 law, carried forward with inflation). Income is then before tax and every amount is in dollars, whatever currency says. "off" (the default, any country) takes income as take-home pay.off
cryptoNoCryptocurrency balance. Default growth 0%.
growthNoDefault portfolio growth rate (percentage). Retirement, Roth, brokerage and HSA balances follow it as the market rate (randomized in Monte Carlo, historical in backtests); it also overrides the fixed defaults of the other assets.
retireNoTarget retirement year (YYYY). Takes precedence over retire_age.
salaryNoAnnual gross salary, as they said it (don't subtract tax). Grows 3%/year, stops at retirement (open-ended if no retirement date is given). The planner doesn't deduct taxes; if they gave a tax amount, include it in expenses.
targetNoAccepted from older links and ignored. The planner answers with a retirement date, not a target.
housingNoMonthly housing expense (rent/mortgage).
marriedNoWith a partner, files jointly. false files as two singles.
pensionNoAnnual pension income. Starts at retirement (immediately if no retirement date is given).
savingsNoHigh-yield savings balance. Default growth 4.5%.
currencyNoDisplay currency. All amounts should be in this currency.USD
expensesNoTotal monthly spending. Send this alone, or categories alone. If both are sent, categories count as part of this total and only the remainder becomes "Monthly expenses" (never added on top). Do not repeat the total as a category.
brokerageNoTaxable brokerage account balance. Default growth 7%.
claim_ageNoAge Social Security is claimed (62-70), for social_security (with birth) or pia.
debt_nameNoName/label for the debt. Default "Debt".
debt_rateNoDebt annual interest rate (percentage).
inflationNoDefault inflation rate (percentage). Overrides individual expense defaults.
insuranceNoMonthly insurance expense.
utilitiesNoMonthly utilities expense.
dependentsNoDependents' birth years (child tax credit until 17, ACA household size).
healthcareNoMonthly healthcare expense.
retire_ageNoTarget retirement age. Requires birth to compute retirement year. Ignored if retire is provided.
retirementNoRetirement account balance (401k, IRA, etc). Default growth 7%.
real_estateNoReal estate equity. Default growth 4%.
side_incomeNoAnnual side hustle / freelance income. Stops at retirement (open-ended if no retirement date is given).
debt_paymentNoMonthly debt payment.
discretionaryNoMonthly discretionary spending.
partner_birthNoA partner's birth year (YYYY). The partner retires at the same time. Every account and income line stays the first person's.
rental_incomeNoAnnual rental income.
transportationNoMonthly transportation expense.
part_time_untilNoAge part_time_income stops (needs birth). Omitted or 100 = for life.
roth_conversionNoRoth conversion ladder from the first retired year, each December from traditional accounts into Roth. fill_12 converts up to the top of the 12% bracket; fixed converts roth_conversion_amount a year; aca stays under the ACA premium credit's income limit.none
social_securityNoAnnual Social Security income. Starts at claim_age when sent with birth; otherwise at the later of retirement and age 67 (uses whichever is known; immediately if neither).
hsa_contributionNoMonthly HSA contribution.
part_time_incomeNoAnnual part-time income in retirement (Barista FIRE). Starts at the retirement date and runs on; with no retirement date given, the plan retires at the earliest date that works with this income.
cash_contributionNoMonthly cash contribution.
roth_contributionNoMonthly Roth account contribution.
crypto_contributionNoMonthly crypto contribution.
savings_contributionNoMonthly savings contribution.
roth_conversion_untilNoAge the conversions stop.
brokerage_contributionNoMonthly brokerage contribution.
roth_conversion_amountNoDollars a year, with roth_conversion=fixed.
retirement_contributionNoMonthly retirement account contribution.
real_estate_contributionNoMonthly real estate contribution (e.g., extra mortgage principal).

Output Schema

NameRequiredDescriptionDefault
urlYesFull URL to open the Fire Planner with pre-populated data.
answerNoThe planner's answer, in its words, as their plan shows it once opened (average returns, today's money, their currency). A field that does not apply is left out. The whole answer is left out once the day's answers are used up (a limit shared by every caller, reset at 00:00 UTC): the link still opens their plan.
params_appliedYesList of parameter names that were recognized and applied.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / part_time_until
      Added value: +{
      +  "description": "Age part_time_income stops (needs birth). Omitted or 100 = for life.",
      +  "example": 60,
      +  "maximum": 100,
      +  "minimum": 30,
      +  "type": "integer"
      +}
  2. Changed2 schema fields changed
    • changedInput schema / properties / claim_age / description
      Previous value: -"Age Social Security is claimed (62-70), with pia."New value: +"Age Social Security is claimed (62-70), for social_security (with birth) or pia."
    • changedInput schema / properties / social_security / description
      Previous value: -"Annual Social Security income. Starts at the later of retirement and age 67 (uses whichever is known; immediately if neither)."New value: +"Annual Social Security income. Starts at claim_age when sent with birth; otherwise at the later of retirement and age 67 (uses whichever is known; immediately if neither)."
  3. Changed1 schema field changed
    • changedOutput schema / properties / answer / properties / assumptions / properties / income / description
      Previous value: -"Each income: its amount, its frequency (monthly, annual, one-time), from (now or YYYY-MM) and until (retirement, never or YYYY-MM), growth."New value: +"Each income: its amount, its frequency (monthly, annual, one-time), from (now, retirement or YYYY-MM) and until (retirement, never or YYYY-MM), growth."
  4. Changed12 schema fields changed
    • addedInput schema / properties / claim_age
      Added value: +{
      +  "default": 67,
      +  "description": "Age Social Security is claimed (62-70), with pia.",
      +  "maximum": 70,
      +  "minimum": 62,
      +  "type": "integer"
      +}
    • addedInput schema / properties / dependents
      Added value: +{
      +  "description": "Dependents' birth years (child tax credit until 17, ACA household size).",
      +  "example": [
      +    2015,
      +    2018
      +  ],
      +  "items": {
      +    "type": "integer"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / married
      Added value: +{
      +  "default": true,
      +  "description": "With a partner, files jointly. false files as two singles.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / partner_birth
      Added value: +{
      +  "description": "A partner's birth year (YYYY). The partner retires at the same time. Every account and income line stays the first person's.",
      +  "example": 1988,
      +  "type": "integer"
      +}
    • addedInput schema / properties / pia
      Added value: +{
      +  "description": "Monthly Social Security benefit at full retirement age, from the SSA statement. The planner computes the benefit for claim_age from it.",
      +  "example": 2400,
      +  "type": "number"
      +}
    • addedInput schema / properties / roth_conversion
      Added value: +{
      +  "default": "none",
      +  "description": "Roth conversion ladder from the first retired year, each December from traditional accounts into Roth. fill_12 converts up to the top of the 12% bracket; fixed converts roth_conversion_amount a year; aca stays under the ACA premium credit's income limit.",
      +  "enum": [
      +    "none",
      +    "fill_10",
      +    "fill_12",
      +    "fill_22",
      +    "fill_24",
      +    "fixed",
      +    "aca"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / roth_conversion_amount
      Added value: +{
      +  "description": "Dollars a year, with roth_conversion=fixed.",
      +  "example": 30000,
      +  "type": "number"
      +}
    • addedInput schema / properties / roth_conversion_until
      Added value: +{
      +  "default": 72,
      +  "description": "Age the conversions stop.",
      +  "type": "integer"
      +}
    • addedInput schema / properties / state
      Added value: +{
      +  "description": "Two-letter US state code (DC too) for state income tax. Without it, federal tax only.",
      +  "example": "CA",
      +  "type": "string"
      +}
    • addedInput schema / properties / taxes
      Added value: +{
      +  "default": "off",
      +  "description": "\"us\" computes US federal, state and payroll tax every year (2026 law, carried forward with inflation). Income is then before tax and every amount is in dollars, whatever currency says. \"off\" (the default, any country) takes income as take-home pay.",
      +  "enum": [
      +    "us",
      +    "off"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / answer / properties / assumptions / properties / taxes
      Added value: +{
      +  "description": "Off (income is take-home pay), or what US taxes on computes with: the state, filing, dependents and the Roth conversion strategy.",
      +  "type": "string"
      +}
    • changedOutput schema / properties / answer / properties / table / description
      Previous value: -"Year by year in today's money, the rows and numbers the planner's Table shows (3 significant figures): the first and last years, every 5th year and the retirement year. Net worth is at the end of each year: on average returns, and the 10th percentile, median and 90th percentile of the Monte Carlo simulations and of the backtest's start years, for each model that ran (0 once the money has run out). Income, spending (debt payments not included) and withdrawals are on the average path. `notes` names a part first year and the years that draw on a retirement account while the early withdrawal penalty applies."New value: +"Year by year in today's money, the rows and numbers the planner's Table shows (3 significant figures): the first and last years, every 5th year and the retirement year. Net worth is at the end of each year: on average returns, and the 10th percentile, median and 90th percentile of the Monte Carlo simulations and of the backtest's start years, for each model that ran (0 once the money has run out). Income, spending (debt payments not included) and withdrawals are on the average path. `notes` names a part first year and the years that draw on a retirement account while the early withdrawal penalty applies. With taxes=us, `tax` is the year's federal, state and payroll tax and `tax_rate_pct` its share of the year's income and withdrawals."
  5. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint true, openWorldHint false, and destructiveHint false. The description goes much further: it explains the return format (answer, coast_number, coast, assumed, missing, table, assumptions), the plan link behavior (shared plan saves nothing, runs in browser, nothing saved until confirm), tax handling, and pre-retirement cash-flow assumptions. This is rich behavioral context beyond 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 description is long but justified for a 52-parameter tool. It is front-loaded with usage and purpose, though some repetition about `missing` and tax defaults could be trimmed. The paragraph-based structure is dense but mostly earns its place given the tool's complexity.

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

Completeness5/5

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

Given the tool's complexity, the description covers purpose, usage, behavioral details, units, tax modes, plan-link behavior, and return fields. The output schema exists, but the description still explains how to interpret the answer and plan link, making it complete for an agent to call and use the tool correctly.

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 the schema already documents every parameter. The description adds cross-cutting semantics: income is annual, expenses and contributions are monthly, amounts are in whole currency units, growth and inflation are percentages, and taxes default to off. It also clarifies how `missing` and `assumed` work, which adds useful meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: it turns what someone has said about their money into firenum's answer and their plan. It clearly covers retirement timing, money lasting, FIRE number, and Coast/Barista/Lean/Fat FIRE variants. The scope is unambiguous even without sibling tools.

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?

It gives explicit when-to-use conditions ('Use when someone asks when they can retire...') and notes that all parameters are optional, with `missing` indicating what to ask for. It also says to call again with `retire` to grade another year. It lacks explicit when-not-to-use guidance, but for a single-tool context the usage is clear.

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