Skip to main content
Glama

TrueCalci

by com.truecalci

compound_wealth

Simulate long-term compound interest growth for retirement portfolios, 401(k)s, Roth IRAs, UK ISAs, or European ETF savings plans (Sparplan) with recurring monthly deposits.

Behavior: Deterministic, idempotent calculation with zero external side effects. Applies discrete compound interest formula with periodic annuity deposits: Future Value = P*(1 + r/n)^(nt) + PMT(((1 + r/n)^(n*t) - 1)/(r/n)). Returns final accumulated balance, total principal contributed, total compound interest earned, and annual wealth progression milestone table.

Usage Guidelines: Use for multi-year personal wealth projection and retirement nest-egg simulations. Do not use for Indian mutual fund monthly SIPs with annual step-up; use sip_investment instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
principalNoInitial lump-sum deposit or starting balance in currency units. Must be non-negative.
tenureYearsYesInvestment horizon in years (e.g. 10, 20, 30). Must be an integer >= 1.
monthlyDepositNoRecurring monthly contribution added to the account. Must be non-negative.
annualRatePercentYesExpected annualized investment return rate percentage (e.g. 8 for 8%). Must be positive.
compoundFrequencyNoNumber of compounding periods per year (1 for annual, 4 for quarterly, 12 for monthly).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed5 schema fields changed
    • changedInput schema / properties / annualRatePercent / description
      Previous value: -"Expected annual return in %"New value: +"Expected annualized investment return rate percentage (e.g. 8 for 8%). Must be positive."
    • changedInput schema / properties / compoundFrequency / description
      Previous value: -"Compounding frequency per year (12 = monthly)"New value: +"Number of compounding periods per year (1 for annual, 4 for quarterly, 12 for monthly)."
    • changedInput schema / properties / monthlyDeposit / description
      Previous value: -"Monthly recurring contribution"New value: +"Recurring monthly contribution added to the account. Must be non-negative."
    • changedInput schema / properties / principal / description
      Previous value: -"Initial principal deposit"New value: +"Initial lump-sum deposit or starting balance in currency units. Must be non-negative."
    • changedInput schema / properties / tenureYears / description
      Previous value: -"Duration in years"New value: +"Investment horizon in years (e.g. 10, 20, 30). Must be an integer >= 1."
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden. It discloses that the calculation is deterministic, idempotent, and has zero external side effects, gives the exact discrete compound interest formula with periodic annuity deposits, and enumerates what it returns. This goes well beyond typical tool descriptions and gives the agent a clear behavioral model.

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?

Three tight paragraphs: purpose, behavior/formula/outputs, and usage guidance. The most decision-relevant information is front-loaded, and every sentence contributes meaning. No filler or redundancy.

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?

Despite having no output schema and no annotations, the description is self-sufficient: it explains the calculation domain, formula, side effects, return values, and routing to an alternative tool. Nothing essential for an agent to select and invoke this tool correctly 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 baseline is 3. The description adds value by explaining the formula with variables (P, r, n, t, PMT), clarifying that monthly deposits are periodic annuity contributions, and describing the outputs. It does not restate each parameter but complements the schema with calculation semantics.

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 ('Simulate') and resource ('long-term compound interest growth'), names relevant use cases (retirement portfolios, 401(k)s, Roth IRAs, UK ISAs, European ETF savings plans), and distinguishes itself from sip_investment by explicitly excluding Indian mutual fund SIPs with annual step-up. An agent can immediately understand what this tool does and how it differs from an important sibling.

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?

Provides explicit guidance: use for multi-year personal wealth projection and retirement nest-egg simulations, and explicitly says not to use it for Indian mutual fund monthly SIPs with annual step-up, directing the agent to sip_investment instead. This is clear when-to-use and when-not-to-use guidance with a named alternative.

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

All TrueCalci toolsInspect
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

A4.4/5.0
Disambiguation5/5

Every tool targets a separate calculation formula or regulatory context, and descriptions include explicit 'do not use... use X instead' cross-references that clearly separate similar calculators. Even overlapping financial/loan/tax tools are disambiguated by geography, employment model, or specific formula.

Naming Consistency4/5

All tool names are lowercase snake_case and follow a domain/acronym-plus-descriptor pattern, making the set visually and structurally consistent. Minor outliers like casio_991_solve and heavy acronyms (npv_irr, scorp_optimizer) prevent it from being perfectly uniform.

Tool Count2/5

At 28 tools, the server is above the 25-tool threshold that makes broad tool scanning costly for an agent. Every calculator is distinct, but the mix of unrelated domains (tax, fluid mechanics, rocket equations, restaurant tips) means most agents will only ever need a small subset.

Completeness4/5

The set covers a wide range of self-contained calculation domains, from finance and tax to physics and everyday bills, with no obvious dead ends—each tool returns a complete result. Missing general-purpose utilities such as unit/currency conversion or descriptive statistics are notable gaps, but they are workaroundable and don't break the server's specialized calculator model.

Resources