Skip to main content
Glama

NPS Calculator

nps_calculator
Read-onlyIdempotent

Pension and lump sum from NPS when you retire. Same calculation as https://paisafinder.com/calculators/nps-calculator. Every input is optional; anything left out uses the default shown in its schema.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nps_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
amtNoMonthly contribution (rupees)
rateNoExpected return (p.a.) (%). NPS equity: 10–12% historical
yearsNoYears to retirement (years)
annuityNoAnnuity return (p.a.) (%)
annuityPctNoAnnuity portion (%). At least 20% since Dec 2025 (40% for government employees)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / annuityPct / default
      Previous value: -40New value: +20
    • changedInput schema / properties / annuityPct / description
      Previous value: -"Annuity portion (%). Minimum 40% mandated"New value: +"Annuity portion (%). At least 20% since Dec 2025 (40% for government employees)"
    • changedInput schema / properties / annuityPct / minimum
      Previous value: -40New value: +20
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety behavior is covered. The description adds that the computation mirrors a specific published calculator, which is a meaningful fidelity signal, but it says nothing about what the response contains (corpus vs. monthly pension split, currency, rounding) despite there being no output schema.

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?

Two short sentences, front-loaded with the outcome, followed by the defaulting rule. The external URL reference is defensible as a fidelity claim but consumes space that could have described the returned outputs.

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?

For a zero-required-parameter calculator with no output schema, the definition should at least characterize the result shape it produces. Saying 'pension and lump sum' hints at outputs but leaves the agent guessing about the actual returned fields and whether pension is monthly or annual.

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 each parameter is already documented with units, bounds, and regulatory context (annuity minimum). The description only restates the defaulting rule and adds no per-parameter meaning beyond the schema, which is the expected baseline.

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 computation and resource: pension and lump-sum corpus from NPS at retirement. An agent can tell this is an NPS-specific projection rather than a generic retirement or lumpsum tool. It does not explicitly differentiate itself from near-neighbors like retirement_calculator or lumpsum_calculator.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Adds useful operating guidance that every input is optional and omitted inputs fall back to schema defaults, which tells the agent it can call with an empty object. It gives no guidance on when to prefer this over sibling retirement/lumpsum calculators or what prerequisites (contribution continuity, corpus assumptions) matter.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources