Skip to main content
Glama
mcp-india-stack

mcp-india-stack

calculate_sip_returns

Read-onlyIdempotent

Calculate SIP maturity with inflation-adjusted returns from monthly investment, expected CAGR, tenure, and inflation to project mutual fund goals.

Instructions

Calculate SIP maturity with inflation-adjusted returns.

Use when projecting mutual fund SIP returns or planning systematic investments.

Args: monthly_investment: Monthly SIP amount expected_annual_return: Expected CAGR % tenure_years: Investment tenure inflation_rate: Expected inflation %

Returns: Corpus with wealth gained and inflation-adjusted value.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "monthly_investment": "<monthly_investment>",
      "expected_annual_return": "<expected_annual_return>",
      "tenure_years": "<tenure_years>"
    },
    "name": "calculate_sip_returns"
  }
}

Input Schema

NameRequiredDescriptionDefault
tenure_yearsYesInvestment tenure in years
financial_yearNoFinancial year (e.g. '2025-26', '2026-27')2025-26
inflation_rateNoExpected inflation rate percentage
monthly_investmentYesMonthly SIP amount in INR
expected_annual_returnYesExpected CAGR as percentage

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.8.0
    • addedInput schema / properties / financial_year
      Added value: +{
      +  "default": "2025-26",
      +  "description": "Financial year (e.g. '2025-26', '2026-27')",
      +  "title": "Financial Year",
      +  "type": "string"
      +}
  2. Changed7 schema fields changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / expected_annual_return / title
      Added value: +"Expected Annual Return"
    • addedInput schema / properties / inflation_rate / title
      Added value: +"Inflation Rate"
    • addedInput schema / properties / monthly_investment / title
      Added value: +"Monthly Investment"
    • addedInput schema / properties / tenure_years / title
      Added value: +"Tenure Years"
    • addedInput schema / title
      Added value: +"calculate_sip_returnsArguments"
    • addedOutput schema / title
      Added value: +"calculate_sip_returnsDictOutput"
  3. Addedv0.4.2

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety and determinism are covered. The description usefully adds that the output is a corpus with wealth gained plus an inflation-adjusted value, but says nothing about compounding conventions, contribution timing, or the role of financial_year.

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 purpose and usage trigger are front-loaded in the first two lines, which is exactly right. The subsequent Args/Returns blocks are largely duplicative of the schema and output schema respectively, so a small amount of text does not earn its place.

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 deterministic read-only calculator with a full input schema, output schema, and annotation coverage, the description covers purpose, trigger and result shape adequately. The only real gap is the unmentioned financial_year parameter and its default, which an agent could overlook when the calculation is year-sensitive.

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 100%, so every parameter is already documented with units ('in INR', 'as percentage') in the schema. The description's Args block mostly restates the schema and omits the financial_year parameter entirely, so it adds essentially no meaning beyond what structured fields provide.

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

Purpose4/5

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

States a specific verb and resource ('Calculate SIP maturity') plus a distinguishing qualifier ('inflation-adjusted returns'), which lets an agent tell it apart from calculate_step_up_sip or calculate_rd_maturity at a glance. The distinction is implicit rather than stated, so it falls short of a 5.

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?

'Use when projecting mutual fund SIP returns or planning systematic investments' gives a clear usage context. It does not, however, state when to prefer the sibling calculate_step_up_sip (for increasing contributions) over this flat-SIP calculator, which is the most likely confusion in this toolset.

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

Deploy Server

Other Tools