Skip to main content
Glama
mcp-india-stack

mcp-india-stack

calculate_sukanya_samriddhi

Read-onlyIdempotent

Calculate Sukanya Samriddhi (SSY) or Senior Citizen Savings Scheme (SCSS) maturity amounts from annual deposits and interest rates, showing interest breakdown and tax status for long-term savings planning.

Instructions

Calculate SSY or SCSS maturity amount.

Use when planning long-term savings for girl child (SSY) or retirement (SCSS).

Args: scheme: "ssy" or "scss" annual_investment: Annual deposit amount annual_interest_rate: Interest rate (default 8.2%)

Returns: Maturity amount with interest breakdown and tax status.

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": {
      "scheme": "<scheme>",
      "annual_investment": "<annual_investment>"
    },
    "name": "calculate_sukanya_samriddhi"
  }
}

Input Schema

NameRequiredDescriptionDefault
schemeYes'ssy' for Sukanya Samriddhi or 'scss' for Senior Citizen Savings Scheme
financial_yearNoFinancial year (e.g. '2025-26', '2026-27')2025-26
annual_investmentYesAnnual deposit amount in INR
annual_interest_rateNoInterest rate 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. Changed6 schema fields changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / annual_interest_rate / title
      Added value: +"Annual Interest Rate"
    • addedInput schema / properties / annual_investment / title
      Added value: +"Annual Investment"
    • addedInput schema / properties / scheme / title
      Added value: +"Scheme"
    • addedInput schema / title
      Added value: +"calculate_sukanya_samriddhiArguments"
    • addedOutput schema / title
      Added value: +"calculate_sukanya_samriddhiDictOutput"
  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 establish readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is covered elsewhere. The description adds that a result includes an interest breakdown and tax status, but it does not disclose key computational assumptions such as scheme tenure (e.g. 15 years for SSY vs 5 for SCSS) or whether the rate is a user override versus the notified rate. Useful but not rich behavioral context beyond the annotations.

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 sentence is front-loaded, followed by a usage sentence and short Args/Returns blocks — structurally easy to scan. The Args section is largely redundant with a fully described schema, costing some efficiency, but nothing is verbose or padded.

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?

With an output schema present, the description need not explain return values, and annotations cover the read-only/idempotent profile; the definition is adequate for a four-parameter projection calculator. The remaining gap is domain assumptions (scheme tenure and rate source) that materially affect the computed maturity figure and are not stated anywhere.

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 schema already documents every parameter including types, defaults, and the 'ssy'/'scss' enum-like choice. The Args block restates three of the four parameters and omits financial_year entirely, so it adds no meaning the schema doesn't already carry. Baseline 3 applies when the schema does the heavy lifting.

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 SSY or SCSS maturity amount') and names both schemes, which separates it from sibling calculators like calculate_ppf_maturity, calculate_fd_maturity, or calculate_nps_projection. It stops short of explicitly contrasting with those siblings, so an agent must infer the distinction from the scheme names rather than being told.

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 long-term savings for girl child (SSY) or retirement (SCSS)' gives a clear triggering context tied to each scheme option. There is no when-not guidance and no mention of the closely related calculators (PPF, NPS, SIP) that an agent might confuse it with, so the routing signal is positive but not exhaustive.

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