Skip to main content
Glama
mcp-india-stack

mcp-india-stack

calculate_step_up_sip

Read-onlyIdempotent

Calculate step-up SIP corpus with annual contribution increases and compare results against a flat SIP for salary-linked investment planning.

Instructions

Calculate SIP with annual step-up increment.

Use when comparing step-up SIP vs flat SIP or planning salary-linked investments.

Args: initial_monthly_investment: Starting SIP amount annual_step_up_percent: % increase each year expected_annual_return: Expected CAGR % tenure_years: Investment tenure

Returns: Corpus comparison between step-up and flat SIP.

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": {
      "initial_monthly_investment": "<initial_monthly_investment>",
      "annual_step_up_percent": "<annual_step_up_percent>",
      "expected_annual_return": "<expected_annual_return>",
      "tenure_years": "<tenure_years>"
    },
    "name": "calculate_step_up_sip"
  }
}

Input Schema

NameRequiredDescriptionDefault
tenure_yearsYesInvestment tenure in years
financial_yearNoFinancial year (e.g. '2025-26', '2026-27')2025-26
annual_step_up_percentYesAnnual step-up percentage
expected_annual_returnYesExpected CAGR as percentage
initial_monthly_investmentYesStarting SIP amount in INR

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 / annual_step_up_percent / title
      Added value: +"Annual Step Up Percent"
    • addedInput schema / properties / expected_annual_return / title
      Added value: +"Expected Annual Return"
    • addedInput schema / properties / initial_monthly_investment / title
      Added value: +"Initial Monthly Investment"
    • addedInput schema / properties / tenure_years / title
      Added value: +"Tenure Years"
    • addedInput schema / title
      Added value: +"calculate_step_up_sipArguments"
    • addedOutput schema / title
      Added value: +"calculate_step_up_sipDictOutput"
  3. Addedv0.4.2

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnlyHint, idempotentHint and closed-world behavior, so the safety profile is covered. The description adds genuine behavioral context beyond that: the result is a corpus comparison between a stepped-up and a flat SIP, not just a single maturity value. It does not state units, rounding, or assumptions about contribution timing, which keeps it from a 5.

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?

Front-loaded one-line purpose, then a usage sentence, then structured Args/Returns blocks — easy to scan with no filler prose. The Args section duplicates schema descriptions almost verbatim, so a small portion of the text does not earn its place.

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?

With a full output schema, the description needn't explain return values, and the annotation set covers safety semantics; what remains is purpose, selection context and input meaning, all present. The only omission, the optional financial_year parameter, is documented in the schema with a default and example, so an agent can still call the tool correctly.

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 description coverage is 100%, so the baseline is 3, and the Args block largely restates the schema glosses (e.g. 'Starting SIP amount' vs 'Starting SIP amount in INR'). More importantly, the description silently omits the fifth parameter financial_year, which is optional with a default and affects which tax-year context the calculation uses.

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 with annual step-up increment' — which is meaningfully narrower than a generic SIP calculator and lets an agent distinguish it from the flat-return sibling. It stops short of naming calculate_sip_returns explicitly as the flat alternative, so differentiation is implied rather than declared.

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 comparing step-up SIP vs flat SIP or planning salary-linked investments' gives concrete usage contexts rather than leaving selection to inference. There is no explicit when-not guidance and the obvious sibling calculate_sip_returns is never named, so an agent must infer which tool handles plain flat SIP.

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