Skip to main content
Glama
rehan1020

mcp-india-stack

by rehan1020
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

calculate_fd_maturity

Read-onlyIdempotent

Calculate the exact fixed deposit maturity amount with interest breakdown, compounding effects, senior citizen benefits, and TDS, to project returns or 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
principalYesDeposit amount in INR
compoundingNomonthly, quarterly, half_yearly, yearly, simplequarterly
tenure_daysYesDeposit tenure in days
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

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. Addedv0.4.2

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, so the basic behavior is covered. The description adds useful detail such as the 0.25% senior citizen extra rate and the ₹40,000/yr TDS threshold, but doesn't disclose rounding rules or day-count conventions beyond the 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?

Purpose is front-loaded and the description is structured into an action sentence, a usage line, parameter notes, and a returns explanation. It is mildly redundant because all argument details already appear in the schema, but it stays readable and doesn't waste 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?

Given the output schema exists and the input schema is fully self-documenting, the description covers the important usage aspects: when to use, what to expect as a return, maturity with interest breakdown, and TDS. It doesn't cover rounding conventions or edge-case inputs, but these are not critical for a maturity calculator tool.

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 schema already documents all parameters. The description enriches a few semantics: it names the compounding frequency allowed values, and adds the clear '0.25% extra rate' and TDS threshold details that the schema omits. This helps the agent provide more accurate inputs.

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 clearly states a specific verb and resource: 'Calculate Fixed Deposit maturity amount.' It identifies the domain and distinguishes it from sibling financial calculators (RD, PPF, SIP), though it doesn't explicitly call out the nearest sibling for contrast.

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?

Provides explicit usage cues with 'Use when projecting FD returns or comparing deposit options.' This tells an agent when the tool is appropriate, though it doesn't mention alternatives like calculate_rd_maturity or explicitly say when not to use it.

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