Skip to main content
Glama

TrueCalci

by com.truecalci
OverviewDiscussionsAdmin

SIP investment returns

sip_investment
Read-onlyIdempotent

Calculate Systematic Investment Plan (SIP) mutual fund maturity wealth with optional annual percentage step-up (top-up) for compounding wealth growth.

Behavior: Deterministic, idempotent calculation with zero external side effects. Models monthly SIP compounding using formula FV = P * [((1 + i)^n - 1) / i] * (1 + i). When stepUpPercent > 0, dynamically increases monthly installment each 12-month cycle. Returns maturity amount, total invested capital, total estimated capital gains, and year-by-year accumulation.

Usage Guidelines: Use for mutual fund SIP investments, recurring deposits, and goal-based financial planning. Do not use for US 401(k) / Roth IRA compounding with lump sum; use compound_wealth instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
as_of_dateYesCivil date YYYY-MM-DD. Selects the rule pack in force on that date. Required: the engine will not assume a date.
tenureYearsNoTotal investment duration in years (e.g. 5, 10, 20). Must be an integer >= 1.
stepUpPercentNoAnnual percentage increase in monthly contribution (e.g. 10 for 10% annual hike).
annualReturnRateNoExpected annualized return rate percentage (e.g. 12 for 12% equity CAGR).
monthlyInvestmentYesMonthly SIP amount in INR as a string with exactly 2 decimal places.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / as_of_date
      Added value: +{
+  "description": "Civil date YYYY-MM-DD. Selects the rule pack in force on that date. Required: the engine will not assume a date.",
+  "example": "2026-09-26",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "monthlyInvestment"
-]New value: +[
+  "monthlyInvestment",
+  "as_of_date"
+]
  2. Changed4 schema fields changed
    • changedInput schema / properties / monthlyInvestment / description
      Previous value: -"Initial monthly investment installment amount in currency units (e.g. 5000). Must be positive."New value: +"Monthly SIP amount in INR as a string with exactly 2 decimal places."
    • addedInput schema / properties / monthlyInvestment / example
      Added value: +"5000.00"
    • addedInput schema / properties / monthlyInvestment / pattern
      Added value: +"^\\d+\\.\\d{2}$"
    • changedInput schema / properties / monthlyInvestment / type
      Previous value: -"number"New value: +"string"
  3. Changed4 schema fields changed
    • changedInput schema / properties / annualReturnRate / description
      Previous value: -"Expected annual return rate in %"New value: +"Expected annualized return rate percentage (e.g. 12 for 12% equity CAGR)."
    • changedInput schema / properties / monthlyInvestment / description
      Previous value: -"Monthly SIP amount"New value: +"Initial monthly investment installment amount in currency units (e.g. 5000). Must be positive."
    • changedInput schema / properties / stepUpPercent / description
      Previous value: -"Annual step-up percentage (e.g. 10 for 10% annual increase)"New value: +"Annual percentage increase in monthly contribution (e.g. 10 for 10% annual hike)."
    • changedInput schema / properties / tenureYears / description
      Previous value: -"Investment duration in years"New value: +"Total investment duration in years (e.g. 5, 10, 20). Must be an integer >= 1."
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds value by specifying the exact compounding formula, the monthly compounding model, the step-up behavior ('dynamically increases monthly installment each 12-month cycle'), and the return values (maturity amount, invested capital, capital gains, year-by-year accumulation). No contradictions with 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 well-structured with labeled 'Behavior' and 'Usage Guidelines' sections, and the purpose is front-loaded. It is efficient, though the phrase 'Deterministic, idempotent calculation with zero external side effects' partially repeats annotations already present, which prevents a top score.

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?

For a read-only, idempotent calculator with 100% schema parameter coverage, the description provides complete usage context, an explicit formula, step-up behavior, and return output description. There is no output schema, but the description compensates by listing what is returned. No significant gaps remain.

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?

Input schema covers all 5 parameters with descriptions, achieving 100% coverage, so the baseline is 3. The description adds meaningful context for stepUpPercent by clarifying it takes effect per 12-month cycle, and it defines the overall calculation context around the parameters. This goes slightly 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 opens with a specific verb and resource: 'Calculate Systematic Investment Plan (SIP) mutual fund maturity wealth' with an optional annual percentage step-up. It clearly distinguishes from sibling compound_wealth by naming what this tool is not for (lump sum US 401(k)/Roth IRA compounding).

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?

Explicitly states when to use: 'Use for mutual fund SIP investments, recurring deposits, and goal-based financial planning' and when not to: 'Do not use for US 401(k) / Roth IRA compounding with lump sum; use compound_wealth instead.' This routes the agent to the correct tool without ambiguity.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources