calculators

project_wealth_plan

Run RetireCrunch's full year-by-year Wealth Plan projection for a household. Models earned income, pensions, expenses, portfolio growth, optional growth→income phase switch, mortgage amortization, optional property sale, and region-aware tax (US uses 2026 federal+state brackets; other regions use a flat rate). Returns a compact summary with 5-year milestones by default, or the full annual array when yearly_detail=true.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`region`	No	Country regime — drives tax model (US uses bracket-based federal/state; others a flat rate).	GENERIC
`currency`	No		USD
`start_year`	Yes	First year of the projection (typically the current year).
`yearly_detail`	No	When true, include the full year-by-year array in the response. When false (default), return a compact summary plus 5-year milestones.
`household_type`	No		single
`inflation_rate`	No	Annual inflation %.
`retirement_year`	Yes	Year retirement begins.
`current_mortgage`	No
`current_property`	No
`current_liquidity`	No
`income_yield_rate`	No	Annual yield % during the income phase.
`estimated_tax_rate`	No	Pre-retirement effective tax rate (%).
`plan_horizon_years`	No	Total years to project from start_year.
`property_sale_year`	No
`current_living_costs`	No	Annual general living expenses today.
`portfolio_volatility`	No	Return std dev %; 0 = deterministic.
`current_earned_income`	No	Annual gross earned income today.
`portfolio_return_rate`	No	Annual real portfolio return %.
`portfolio_switch_year`	No	Year to switch from growth to income phase. Defaults to retirement_year if omitted.
`property_sale_enabled`	No
`current_other_expenses`	No	Annual other expenses today.
`current_housing_expenses`	No	Annual housing expenses today.
`portfolio_switch_enabled`	No
`post_retirement_tax_rate`	No	Post-retirement effective tax rate (%).
`property_sale_destination`	No		liquidity
`current_investment_portfolio`	No
`partner_survivor_expense_factor`	No
`partner_early_death_years_before_end`	No

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well. It discloses the regional tax model (US 2026 brackets vs flat rate), optional phase switch and property sale, and the default vs full output behavior via yearly_detail. It does not cover edge cases or assumptions, but for a read-only computation tool this is substantial behavioral context beyond the schema.

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?

The description is two sentences, front-loaded with the primary action, followed by model details and output behavior. Every clause adds information with no redundancy or off-topic content.

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 tool with 28 parameters and no output schema, the description is thorough: it covers scope, modeled components, regional tax differences, and output format. It does not specify exact fields in the summary or milestones, but it is sufficient for an agent to understand the tool's role and toggle yearly_detail. Slightly more detail on return structure would make it a 5.

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 coverage is 57%, and the description adds context for some parameters (e.g., 'growth→income phase switch' maps to portfolio_switch_enabled/year, 'optional property sale' maps to property_sale_enabled/year, 'region-aware tax' maps to region). However, many parameters receive no added meaning from the description, leaving the agent to rely on schema descriptions or defaults for obscure fields like partner_early_death_years_before_end.

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 clearly states the tool runs a full year-by-year Wealth Plan projection for a household, with a specific verb ('Run') and resource. It enumerates modeled components (income, pensions, expenses, portfolio growth, phase switch, mortgage, property sale, taxes), which distinguishes it from siblings focused on standalone FIRE calculations, property tax, or portfolio returns.

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?

The description implies usage for comprehensive household wealth projections by outlining the modeled scenarios and output options, but it does not explicitly mention alternatives or exclusions. An agent can infer this is for full projections rather than single-purpose calculations, but explicit comparison to siblings is absent.

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

All calculators tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation5/5

Each tool targets a clearly distinct financial calculation or data retrieval purpose. Coast FIRE, FIRE target, Swiss property tax, portfolio returns, wealth projection, and rebalancing have no overlapping responsibilities.

Naming Consistency3/5

All names are snake_case, but the verb prefixes are inconsistent: calculate_, compute_, get_, project_, rebalance_. The use of both 'calculate' and 'compute' for similar actions plus other varied verbs creates a noticeable lack of a single pattern.

Tool Count5/5

Six tools is well-scoped for a financial calculator server. Each tool covers a distinct aspect of retirement and wealth planning without redundancy or bloat.

Completeness4/5

The set covers core retirement planning needs: target calculation, projection, returns data, and rebalancing. The Swiss property tax tool is a specific gap-filler. Missing general tax or simple interest tools, but not critical given the stated focus.

Resources

Need Help?