TrueCalci

India Public Provident Fund

ppf

Read-onlyIdempotent

Simulate Public Provident Fund (PPF) 15-year statutory compound wealth accumulation under Ministry of Finance notifications. Enforces ₹1,50,000 annual deposit ceiling, current 7.1% p.a. sovereign interest rate, monthly 5th day balance compounding rules, and Section 80C EEE tax-exempt maturity.

Input Schema

TableJSON Schema

Name	Required	Description
`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.
`tenure_years`	No	PPF tenure in years (initial 15 years, extendable in 5-year blocks).
`yearly_deposit`	Yes	Annual deposit amount in INR (₹500 to ₹1,50,000).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`trace`	No
`status`	No
`currency`	No
`as_of_date`	No
`disclaimer`	No
`minor_units`	No
`tenure_years`	No
`rule_ids_used`	No
`total_invested`	No
`maturity_amount`	No
`projection_from`	No
`yearly_schedule`	No
`deposit_day_of_month`	No
`start_financial_year`	No
`total_interest_earned`	No
`fifth_day_rule_applied`	No
`statutory_annual_limit`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 27, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "as_of_date": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "currency": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "deposit_day_of_month": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "disclaimer": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "fifth_day_rule_applied": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "maturity_amount": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "minor_units": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "projection_from": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "rule_ids_used": {
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "start_financial_year": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "status": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "statutory_annual_limit": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "tenure_years": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "total_interest_earned": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "total_invested": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "trace": {
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "yearly_schedule": {
+      "type": [
+        "array",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

Changed2 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 / required

Previous value: -[
-  "yearly_deposit"
-]New value: +[
+  "yearly_deposit",
+  "as_of_date"
+]

Changed1 schema field changedSep 24, 2026
- removedInput schema / properties / yearly_deposit / default
```
Removed value: -150000
```
AddedSep 11, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations declare readOnlyHint/idempotentHint/non-destructive, so the safety profile is covered; the description adds substantial domain behavior beyond that — the ₹1,50,000 ceiling, 7.1% rate, monthly 5th-day compounding rule, and Section 80C EEE treatment. It doesn't disclose error or edge-case handling (e.g., deposits exceeding the ceiling), keeping it below 5.

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?

A single dense sentence that front-loads purpose and then stacks the governing rules; nothing is wasted. It is slightly packed, but every clause carries domain value.

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, return values need not be explained, and the description covers the rule pack, rate, ceiling, and tax treatment. What remains missing is routing guidance among sibling instruments, which is a minor gap for a self-contained simulator.

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 all three parameters, including the date's rule-pack semantics and tenure extension. The description adds the deposit ceiling and rate context but no new parameter-level syntax or format detail. Baseline 3 is appropriate.

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?

Names a specific verb (Simulate) and resource (Public Provident Fund 15-year statutory compound wealth accumulation), scoping it to Ministry of Finance rules. An agent can distinguish it from fd, sukanya, and compound_wealth without opening the schema.

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?

The description implies the usage context (Indian sovereign savings scheme simulation) but never states when to choose this over close siblings like fd, sukanya, or compound_wealth, nor any exclusions. Usage is inferable but not directed.

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?