Skip to main content
Glama

PPF Calculator

ppf_calculator
Read-onlyIdempotent

What your PPF account will be worth, tax-free. Same calculation as https://paisafinder.com/calculators/ppf-calculator. Every input is optional; anything left out uses the default shown in its schema.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ppf_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
amtNoAnnual deposit (rupees). Max ₹1.5L per FY
rateNoPPF interest rate (p.a.) (%). Govt revises quarterly
yearsNoDuration (years)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile needs no repetition. The description adds two genuinely useful facts beyond them: the result is tax-free and that omitted inputs fall back to schema defaults, but it says nothing about the shape of the returned figure (single corpus value vs. year-by-year schedule).

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?

Two short sentences, front-loaded with the payoff (what the account will be worth) before the implementation notes. The reference URL and the defaults sentence each earn their place, though the URL adds little for an agent that cannot browse.

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 three-parameter, closed-world calculator with a fully documented schema and explicit annotations, the description covers the essentials. The remaining gap is the return value: with no output schema, the description does not state whether the answer is a single maturity amount or a contribution/interest breakdown.

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 coverage is 100% and every parameter carries its own description, unit, range and default, so the schema does the heavy lifting. The description's only parameter-related contribution – that all inputs are optional and defaulted – restates what the schema already encodes via required: [] and default values.

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 names the resource precisely (PPF account maturity value) and adds a distinguishing property (tax-free), which separates it from siblings like epf_calculator or nps_calculator. It stops short of an explicit verb-plus-output statement such as "calculates the projected maturity corpus," so the purpose is clear but not maximally sharp.

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?

Usage is only implied by "What your PPF account will be worth" – the agent must infer that this is the tool for PPF projections rather than, say, EPF or NPS. There is no explicit when-to-use / when-not-to-use guidance and no named alternative, though the ppf-specific framing makes the intended case reasonably evident.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources