Skip to main content
Glama
mcp-india-stack

mcp-india-stack

calculate_rd_maturity

Read-onlyIdempotent

Compute recurring deposit maturity amount and total interest from monthly installment, annual rate, and tenure to project RD returns and plan deposits.

Instructions

Calculate Recurring Deposit maturity amount.

Use when projecting RD returns or planning recurring deposits.

Args: monthly_installment: Monthly deposit amount annual_interest_rate: Annual rate as percentage tenure_months: Deposit tenure in months

Returns: Maturity amount with total interest earned.

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_installment": "<monthly_installment>",
      "annual_interest_rate": "<annual_interest_rate>",
      "tenure_months": "<tenure_months>"
    },
    "name": "calculate_rd_maturity"
  }
}

Input Schema

NameRequiredDescriptionDefault
tenure_monthsYesDeposit tenure in months
financial_yearNoFinancial year (e.g. '2025-26', '2026-27')2025-26
monthly_installmentYesMonthly deposit amount in INR
annual_interest_rateYesAnnual interest 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 / monthly_installment / title
      Added value: +"Monthly Installment"
    • addedInput schema / properties / tenure_months / title
      Added value: +"Tenure Months"
    • addedInput schema / title
      Added value: +"calculate_rd_maturityArguments"
    • addedOutput schema / title
      Added value: +"calculate_rd_maturityDictOutput"
  3. Addedv0.4.2

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description adds that the result includes total interest earned, but that is already captured by the output schema, and it omits material behavior such as the compounding convention used for RD interest and how financial_year influences the result.

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 with the core purpose in one sentence, followed by a short usage line and a compact Args/Returns block. The Args section largely duplicates the schema, which is mild waste, but overall it is well organized and easy to scan.

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 and read-only annotations present, the description only needs to establish purpose and inputs, which it does. The one gap is that financial_year, an optional fourth parameter, is not mentioned in the description, leaving its role unstated even though the schema defines its format.

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, including the optional financial_year with its format example. The description's Args section merely restates the schema and is actually less precise (it drops 'in INR' and omits financial_year entirely), adding no meaning beyond the structured fields.

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 Recurring Deposit maturity amount,' which is immediately understandable. It lacks any differentiation from the several closely related sibling calculators (calculate_fd_maturity, calculate_ppf_maturity, calculate_sip_returns), so an agent must infer the distinction from the name alone.

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?

'Use when projecting RD returns or planning recurring deposits' gives a usage context but no exclusions or named alternatives among the many sibling maturity calculators. The agent gets implied guidance rather than an explicit rule for choosing this over calculate_fd_maturity or calculate_sip_returns.

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