Skip to main content
Glama
mcp-india-stack

mcp-india-stack

calculate_nps_projection

Read-onlyIdempotent

Project NPS retirement corpus and monthly pension from monthly contributions, current age, and expected returns to plan retirement income.

Instructions

Calculate NPS corpus and monthly pension at retirement.

Use when planning retirement with NPS or projecting pension.

Args: monthly_contribution: Monthly NPS contribution current_age: Current age retirement_age: Retirement age (default 60) expected_annual_return: Expected annual return % annuity_rate: Annuity rate % annuity_percent: % of corpus to buy annuity (min 40%)

Returns: Projected corpus, lump sum, and monthly pension estimate.

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_contribution": "<monthly_contribution>",
      "current_age": "<current_age>"
    },
    "name": "calculate_nps_projection"
  }
}

Input Schema

NameRequiredDescriptionDefault
current_ageYesCurrent age
annuity_rateNoAnnuity rate percentage
financial_yearNoFinancial year (e.g. '2025-26', '2026-27')2025-26
retirement_ageNoRetirement age
annuity_percentNoCorpus for annuity (min 40%)
monthly_contributionYesMonthly NPS contribution in INR
expected_annual_returnNoExpected annual return 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. Changed9 schema fields changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / annuity_percent / title
      Added value: +"Annuity Percent"
    • addedInput schema / properties / annuity_rate / title
      Added value: +"Annuity Rate"
    • addedInput schema / properties / current_age / title
      Added value: +"Current Age"
    • addedInput schema / properties / expected_annual_return / title
      Added value: +"Expected Annual Return"
    • addedInput schema / properties / monthly_contribution / title
      Added value: +"Monthly Contribution"
    • addedInput schema / properties / retirement_age / title
      Added value: +"Retirement Age"
    • addedInput schema / title
      Added value: +"calculate_nps_projectionArguments"
    • addedOutput schema / title
      Added value: +"calculate_nps_projectionDictOutput"
  3. Addedv0.4.2

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so safety and determinism are covered. The description adds the return shape (corpus, lump sum, monthly pension) and the annuity_percent floor of 40%, but says nothing about assumptions embedded in the projection (contribution constancy, return compounding) or the annuity-vs-lump-sum split logic.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening purpose and "Use when" line are well front-loaded, but the docstring-style Args/Returns sections duplicate fields the schema already documents in full and drop one parameter, so a nontrivial share 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.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the Returns note is optional rather than essential. However, with 7 parameters the description's enumeration is incomplete (financial_year is never mentioned), and the interaction between financial_year and contribution limits or tax treatment is left unexplained for what is a multi-input financial projection.

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. The Args block largely restates the schema field descriptions verbatim ("Monthly NPS contribution", "Retirement age", "Annuity rate %") and adds no interpretation, while conspicuously omitting the financial_year parameter that exists in 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 first sentence names a specific verb (calculate) and two concrete outputs (NPS corpus and monthly pension at retirement), which cleanly separates it from adjacent calculators like calculate_ppf_maturity, calculate_sip_returns, and calculate_gratuity in the sibling list.

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 planning retirement with NPS or projecting pension" gives a clear usage context, but it names no exclusions or alternatives, so an agent deciding between this and calculate_ppf_maturity or calculate_sip_returns gets no explicit routing rule.

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