Skip to main content
Glama

Compare saving and investing the same money

smartfin_calculate_savings_vs_investing
Read-onlyIdempotent

Compares the modeled balances of a savings account and of an investment after 1 to 50 years, from the same starting amount and the same monthly contribution, the way SmartFin's savings vs investing calculator does. You give the savings rate and the investment return; each is held the same every year. Optional: a yearly increase in the monthly contribution (or one that follows inflation), a yearly fee on investments, and tax on savings interest or investment gains. Returns both modeled balances, money put in, interest, growth, fees and taxes, the difference, the same figures in today's money, the investment return at which both end the same (when a fee or tax is given), and a fixed falling-returns case at −2% a year. Use for questions like "how do 10,000 in savings at 4% and the same amount invested at 7% compare after 20 years" or "how far apart do saving and investing end after 20 years". It reports two modeled balances and does not say which option to choose. Do not use it for historical stock or index returns (use smartfin_compare_investment_strategies) or for account types and their tax rules, which it does not model. Amounts can be in any one currency; none is converted.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "smartfin_calculate_savings_vs_investing"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearsNoYears to compare, 1 to 50. A decimal is rounded to the nearest whole year. Default 10
currencyNoCurrency for the amounts in the summary and the link. Default USD; amounts are never converted
inflation_pctNoInflation, % a year. Used to show balances in today's money, and to set the yearly increase when step_up_matches_inflation is true. Default 3
starting_amountNoAmount in the account at the start, in the currency chosen below; the same for both paths. Default 10000
savings_rate_pctNoSavings account rate, % a year, with compounding included (APY in the US, AER in the UK). Held the same every year. Default 3
investment_fee_pctNoYearly fee on investments, % a year, subtracted from the return (6% with a 1% fee grows at 5%). Default 0
monthly_contributionNoAmount added to both paths at the end of every month, in the same currency. Default 500
investment_return_pctNoInvestment return before any fee, % a year; may be negative. Held the same every year. Default 6
contribution_step_up_pctNoYearly increase in the monthly contribution, % a year. Year 1 is the amount given; each later year rises by this. Ignored when step_up_matches_inflation is true. Default 0
investment_gains_tax_pctNoTax on investment gains, % of the gains, taken once as if the investments were sold at the end of the years. A simplified assumption, not tax advice. Default 0
savings_interest_tax_pctNoTax on savings interest, % of the interest, taken as the interest is credited. A simplified assumption, not tax advice. Default 0
step_up_matches_inflationNoTrue: each later year's monthly contribution changes by inflation_pct instead of contribution_step_up_pct. Default false

Output Schema

NameRequiredDescriptionDefault
citeYesHow to credit this result
dataYes
nextYesSuggested follow-up calls
linksYes
how_toYesSteps for the user to see or redo this on smartfin.fyi
sourceYes
summaryYesPlain-language result the assistant can quote

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only establish the safety profile (readOnly, idempotent, closed-world), and the description adds substantial modeling context beyond them: rates are held constant every year, tax is taken as a simplified one-time assumption, fees are subtracted from return, balances are also shown in today's money, a fixed −2%/year case is included, and no currency conversion occurs. For a pure calculator this is unusually rich disclosure of assumptions and limits.

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?

Purpose and scope are front-loaded, and the paragraph follows a logical purpose -> inputs -> outputs -> examples -> exclusions order. It is somewhat long for a calculator, and the detailed enumeration of returned figures ('both modeled balances, money put in, interest, growth, fees and taxes...') partly duplicates the output schema, which costs a point.

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 a 12-parameter tool with an output schema, the description covers everything an agent needs: modeling assumptions, which parameters are optional, the constant-rate simplification, the no-conversion currency rule, sibling alternatives, and the fact that it does not give a recommendation. Nothing material is missing.

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 description coverage is 100%, so the schema already defines every parameter; baseline is 3. The description adds value by grouping the inputs into core (savings rate, investment return, both held constant) versus optional features (contribution step-up or inflation-linked, investment fee, interest/gains tax), which helps an agent understand how the 12 parameters interact before diving into 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?

States a specific verb and resource ('Compares the modeled balances of a savings account and of an investment') plus scope (1-50 years, same starting amount and contribution), and explicitly distinguishes itself from siblings by naming smartfin_compare_investment_strategies for historical returns. It also clarifies what it does not do ('does not say which option to choose'), so an agent can select it unambiguously.

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

Usage Guidelines5/5

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

Gives concrete trigger examples ('how do 10,000 in savings at 4% and the same amount invested at 7% compare after 20 years') and explicit exclusions with the alternative tool named for each (historical index returns -> smartfin_compare_investment_strategies; account types/tax rules -> not modeled). This is textbook when-to-use / when-not-to-use guidance.

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