Skip to main content
Glama

EPF Calculator

epf_calculator
Read-onlyIdempotent

What your EPF will be worth at retirement. Same calculation as https://paisafinder.com/calculators/epf-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": "epf_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
hikeNoAnnual salary hike (%)
rateNoEPF rate (p.a.) (%)
basicNoBasic + DA (monthly) (rupees). If your employer caps PF at ₹15,000 wages, enter 15,000
yearsNoYears to retirement (years)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / basic / description
      Previous value: -"Basic salary (monthly) (rupees)"New value: +"Basic + DA (monthly) (rupees). If your employer caps PF at ₹15,000 wages, enter 15,000"
  2. 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=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description usefully adds that omitted inputs silently fall back to schema defaults and that it mirrors an external reference calculator, but says nothing about what the response contains or how the projection is computed.

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?

Three short sentences, front-loaded with the outcome, then the calculation reference, then the optionality rule. The external URL is arguably expendable, but nothing is padded or buried.

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 zero-required-parameter read-only calculator with a fully documented schema and no output schema, the definition covers purpose, defaults behavior, and authoritative reference. The only real gap is that it never characterizes the return value (corpus only, or a year-by-year 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 description coverage is 100% and every parameter carries units, defaults, and min/max bounds, so the schema does the heavy lifting. The description only points back at those defaults and adds no new semantics such as how hike interacts with basic over the horizon; baseline 3 is appropriate.

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 opening sentence states a concrete outcome — projecting EPF value at retirement — which is specific enough to separate it from ppf_calculator, nps_calculator, and retirement_calculator by resource. It does not explicitly name or contrast any sibling, so it stops short of a 5.

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 definition explains how to call it (all inputs optional, defaults applied) but never says when to choose this over the many other retirement/savings calculators. Usage is implied by the EPF label rather than stated, and no exclusions are given.

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