Skip to main content
Glama

TrueCalci

by com.truecalci
OverviewDiscussionsAdmin

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
NameRequiredDescriptionDefault
as_of_dateYesCivil date YYYY-MM-DD. Selects the rule pack in force on that date. Required: the engine will not assume a date.
tenure_yearsNoPPF tenure in years (initial 15 years, extendable in 5-year blocks).
yearly_depositYesAnnual deposit amount in INR (₹500 to ₹1,50,000).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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"
+]
  2. Changed1 schema field changed
    • removedInput schema / properties / yearly_deposit / default
      Removed value: -150000
  3. Added

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already mark the tool read-only and idempotent, and the description adds independently valuable behavioral constraints: the ₹1,50,000 deposit ceiling, the 7.1% p.a. rate, monthly 5th-day balance compounding, and Section 80C tax-exempt treatment. An agent can predict the simulation rules precisely.

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?

The entire description is one dense, front-loaded sentence that begins with the core action and packs each subsequent clause with a binding rule. There is no filler or repetition of the title.

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?

Between the annotations, the fully documented schema, and the description's statutory rules, the agent has almost everything needed to call the tool correctly. The only real gap is the absence of an output schema or any statement of the return shape, so the returned value (maturity corpus vs. schedule) remains slightly ambiguous.

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?

The input schema already documents all three parameters at 100% coverage with clear descriptions, including the ceiling and default tenure. The prose description enriches the domain context (rate, compounding, tax status) but does not add per-parameter meaning on top of the schema, so the baseline of 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?

The description names the action ('Simulate'), the exact instrument ('Public Provident Fund'), and the scope ('15-year statutory compound wealth accumulation under Ministry of Finance notifications'). This is specific enough to distinguish PPF from finance siblings like fd, sukanya, and sip without needing to open their schemas.

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?

When to use the tool is implied by the resource-specific language—PPF, sovereign, Section 80C—so an agent can infer the use case. However, the description never states explicit conditions, exclusions, or alternatives, e.g., when to prefer sukanya or fd instead.

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

All TrueCalci toolsInspect
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