Skip to main content
Glama

Retirement Calculator

retirement_calculator
Read-onlyIdempotent

How much money you need to retire, and the monthly saving to get there. Same calculation as https://paisafinder.com/calculators/retirement-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": "retirement_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageNoCurrent age
lifeNoLife expectancy
retireNoRetirement age
expenseNoMonthly expense (today) (rupees)
preRateNoPre-retirement return (%)
postRateNoPost-retirement return (%)
inflationNoInflation (%)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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, destructiveHint=false and openWorldHint=false, so the safety and determinism profile needs no restating. The description adds real value by disclosing the two result quantities (corpus target and required monthly saving) in the absence of an output schema, plus the default-fallback rule; however it does not say whether results are nominal or inflation-adjusted, nor what currency/unit the output is in.

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

Conciseness5/5

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

Two sentences with the deliverable front-loaded and the fallback rule trailing; nothing is redundant. The external reference link is compact and conveys calculation fidelity in a few words.

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 seven-parameter, fully documented calculator with no output schema, the description covers what the tool returns and how partial inputs are handled, which is the main gap risk. Missing is unit/currency context for the results (rupees appears only in the schema) and whether figures are in today's money or future nominal value.

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% with per-parameter descriptions, defaults and min/max bounds, so the schema carries the semantics. The description adds only one piece of meaning beyond it — that any omitted input silently uses its schema default — which is useful but thin against seven parameters.

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?

The description names a concrete output pair — the retirement corpus needed and the monthly saving required to reach it — which is more specific than the title alone. It does not explicitly differentiate itself from nearby tools such as nps_calculator or project_sip, but the retirement-specific framing is clear enough to select on.

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?

It supplies invocation guidance by stating every input is optional and omitted values fall back to schema defaults, which tells an agent a zero-argument call is valid. It gives no when-to-use vs when-not guidance and names no alternative tool for overlapping goals like pension projection or SIP planning, leaving the routing decision to inference.

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