Skip to main content
Glama
mcp-india-stack

mcp-india-stack

calculate_fd_maturity

Read-onlyIdempotent

Calculate Fixed Deposit maturity amounts in INR with interest breakdown, compounding options, senior citizen rates, and TDS deduction. Use it to project FD returns and compare deposit options.

Instructions

Calculate Fixed Deposit maturity amount.

Use when projecting FD returns or comparing deposit options.

Args: principal: Deposit amount in INR annual_interest_rate: Rate as percentage tenure_days: Deposit tenure in days compounding: Compounding frequency is_senior_citizen: Senior citizen flag (0.25% extra rate) tds_applicable: Apply TDS if interest > ₹40,000/yr

Returns: Maturity amount with interest breakdown and TDS if applicable.

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": {
      "principal": "<principal>",
      "annual_interest_rate": "<annual_interest_rate>",
      "tenure_days": "<tenure_days>"
    },
    "name": "calculate_fd_maturity"
  }
}

Input Schema

NameRequiredDescriptionDefault
principalYesDeposit amount in INR
compoundingNomonthly, quarterly, half_yearly, yearly, simplequarterly
tenure_daysYesDeposit tenure in days
financial_yearNoFinancial year (e.g. '2025-26', '2026-27')2025-26
tds_applicableNoApply 10% TDS if interest exceeds threshold
is_senior_citizenNoSenior citizen flag
annual_interest_rateYesInterest rate as percentage (e.g., 6.5)

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 / annual_interest_rate / title
      Added value: +"Annual Interest Rate"
    • addedInput schema / properties / compounding / title
      Added value: +"Compounding"
    • addedInput schema / properties / is_senior_citizen / title
      Added value: +"Is Senior Citizen"
    • addedInput schema / properties / principal / title
      Added value: +"Principal"
    • addedInput schema / properties / tds_applicable / title
      Added value: +"Tds Applicable"
    • addedInput schema / properties / tenure_days / title
      Added value: +"Tenure Days"
    • addedInput schema / title
      Added value: +"calculate_fd_maturityArguments"
    • addedOutput schema / title
      Added value: +"calculate_fd_maturityDictOutput"
  3. Addedv0.4.2

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare a safe, idempotent, closed-world read, so the description is free to add domain behaviour instead of repeating it. It does exactly that, disclosing the 0.25% senior-citizen rate uplift and the ₹40,000/yr interest threshold that governs TDS. It stops short of stating assumptions such as day-count convention or whether TDS is deducted at source versus merely reported.

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?

Purpose and usage are front-loaded in the first two lines, followed by a scannable Args block and a short Returns line. Nothing is filler, though the Args section largely mirrors the schema and could have been trimmed in favour of the two rules it uniquely adds.

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?

An output schema exists, so the description need not detail the return payload, and its single Returns line is sufficient framing. The omissions are minor but real: financial_year is undocumented and the interaction between financial_year and the TDS threshold is left unstated for a 7-parameter tax-adjacent calculation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns the extra point by attaching business meaning to two flags rather than restating them – is_senior_citizen is tied to a 0.25% rate bump and tds_applicable to the ₹40,000/yr threshold. The one gap is that the financial_year parameter is never mentioned, despite it plausibly affecting TDS threshold behaviour.

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 first line states a specific verb and resource: 'Calculate Fixed Deposit maturity amount.' An agent can immediately tell this is an FD-specific projection tool. It does not, however, distinguish itself from near-neighbours such as calculate_rd_maturity, calculate_ppf_maturity, or calculate_sukanya_samriddhi, so sibling disambiguation rests on the tool 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 Guidelines4/5

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

'Use when projecting FD returns or comparing deposit options' gives a clear usage context rather than leaving it implied. There is no explicit when-not guidance and no named alternative for the recurring-deposit or PPF cases, so the routing signal is positive but incomplete.

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