TrueCalci

Fixed deposit maturity

fd

Read-onlyIdempotent

Calculate Bank and Corporate Fixed Deposit (FD) maturity amount and interest returns. Computes quarterly, monthly, half-yearly, and cumulative compounding with Section 194A TDS threshold analysis (₹40,000 general / ₹50,000 senior citizens).

Input Schema

TableJSON Schema

Name	Required	Description
`principal`	Yes	Deposit amount in INR. At least 1,000 (statutory minimum FD principal, RBI Master Direction 2016).
`as_of_date`	Yes	Civil date YYYY-MM-DD. Selects the rule pack in force on that date. Required: the engine will not assume a date.
`interest_rate`	Yes	Annual interest rate in percent, as a decimal string (e.g. 7.00).
`tenure_months`	Yes	Deposit tenure in months (3 to 120, as the fixed deposit rule pack allows).
`compounding_convention`	No	Read-only. Compounding is fixed by the statutory rule pack in force, not chosen by the caller: Indian bank fixed deposits compound quarterly by RBI convention. Supplying any other value does not change the computation, so only the supported convention is listed. The value actually applied is returned in the response as compounding_convention.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedSep 26, 2026

addedInput schema / properties / as_of_date

Added value: +{
+  "description": "Civil date YYYY-MM-DD. Selects the rule pack in force on that date. Required: the engine will not assume a date.",
+  "example": "2026-09-26",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}

changedInput schema / properties / tenure_months / description

Previous value: -"Deposit tenure in months."New value: +"Deposit tenure in months (3 to 120, as the fixed deposit rule pack allows)."

addedInput schema / properties / tenure_months / example
```
Added value: +12
```
addedInput schema / properties / tenure_months / maximum
```
Added value: +120
```
addedInput schema / properties / tenure_months / minimum
```
Added value: +3
```

changedInput schema / required

Previous value: -[
-  "principal",
-  "interest_rate",
-  "tenure_months"
-]New value: +[
+  "principal",
+  "interest_rate",
+  "tenure_months",
+  "as_of_date"
+]

Changed7 schema fields changedSep 26, 2026

changedInput schema / properties / interest_rate / description

Previous value: -"Annual interest rate in percent (e.g. 7.25 for 7.25%)."New value: +"Annual interest rate in percent, as a decimal string (e.g. 7.00)."

addedInput schema / properties / interest_rate / example
```
Added value: +"7.00"
```
addedInput schema / properties / interest_rate / pattern
```
Added value: +"^\\d+(\\.\\d+)?$"
```
changedInput schema / properties / interest_rate / type
```
Previous value: -"number"New value: +"string"
```

changedInput schema / properties / principal / description

Previous value: -"Deposit principal amount in INR (₹)."New value: +"Deposit amount in INR. At least 1,000 (statutory minimum FD principal, RBI Master Direction 2016)."

addedInput schema / properties / principal / example
```
Added value: +250000
```
addedInput schema / properties / principal / minimum
```
Added value: +1000
```

Changed2 schema fields changedSep 24, 2026

addedInput schema / properties / compounding_convention

Added value: +{
+  "description": "Read-only. Compounding is fixed by the statutory rule pack in force, not chosen by the caller: Indian bank fixed deposits compound quarterly by RBI convention. Supplying any other value does not change the computation, so only the supported convention is listed. The value actually applied is returned in the response as compounding_convention.",
+  "enum": [
+    "quarterly_compounding"
+  ],
+  "type": "string"
+}

removedInput schema / properties / compounding_frequency

Removed value: -{
-  "default": "quarterly",
-  "description": "Interest compounding frequency.",
-  "enum": [
-    "quarterly",
-    "monthly",
-    "half_yearly",
-    "annual",
-    "simple"
-  ],
-  "type": "string"
-}

AddedSep 11, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context: it discloses that compounding is fixed by statutory rule pack, that TDS thresholds are analyzed, and that the computation is rule-based. The schema's compounding_convention parameter also reinforces the fixed-convention behavior. No contradiction with annotations.

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 zero waste. The first sentence states the core function and the second adds the key statutory context. Every clause earns its place, and the most important information (what it calculates) is front-loaded.

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 read-only calculation tool with 100% schema coverage and no output schema, the description is nearly complete. It covers the product scope, compounding conventions, and TDS analysis. The only minor gap is that it doesn't describe the return value shape, but since there is no output schema and the tool is a calculator, the agent can infer a numeric result. The statutory context provided is sufficient for correct invocation.

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 description coverage is 100%, so the schema already documents all parameters thoroughly. The description adds value by explaining the statutory basis (RBI Master Direction, Section 194A) and clarifying that compounding_convention is read-only and fixed. This goes beyond the schema's own descriptions, which already note the statutory constraints. A 4 is appropriate because the description reinforces and contextualizes the parameter semantics without needing to repeat schema details.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Calculate') and resource ('Bank and Corporate Fixed Deposit maturity amount and interest returns'), and enumerates the compounding conventions and TDS threshold analysis. This clearly distinguishes it from sibling tools like home_loan_emi or sip_investment, which address different financial products.

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?

The description implies when to use this tool: when an agent needs FD maturity or interest calculations, including TDS threshold analysis. It doesn't explicitly name alternatives or exclusions, but the specificity of the FD domain and the mention of statutory thresholds provides clear context. A small gap is the lack of explicit 'use this instead of X' guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All TrueCalci tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?