Skip to main content
Glama

Term Policy Ladder

term_policy_ladder_calculator
Read-onlyIdempotent

Split life cover into policies that end at different times, and pay less. Same calculation as https://paisafinder.com/calculators/term-policy-ladder-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": "term_policy_ladder_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageNoCurrent age (years)
kidsYearsNoYears till kids independent (years)
retireAgeNoRetirement age (years)
totalCoverNoTotal cover needed (rupees)
liabilityYearsNoYears till loans clear (years). When home loan, etc. will be done
annualPremiumPerCrNoAnnual Premium (per ₹1Cr) (rupees). Check current quote for single policy till retirement

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, non-destructive and closed-world, so the safety profile is fully covered by structured data. The description adds the reassurance that results match a known public calculator, but says nothing about what the response contains — a notable gap since no output schema exists.

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 with the core mechanism front-loaded and no filler. The external URL is arguably dispensable for an agent but is at most one clause of waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Inputs are fully specified via schema and safety via annotations, but a calculator tool with no output schema leaves the agent guessing what comes back — presumably a ladder split and premium savings, which the description never states. Adding a sentence on return values would close the only real gap.

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 all six parameters, their units, ranges and defaults are already documented. The description adds only the meta-point that all inputs are optional with schema-listed defaults, which is helpful but does not add per-parameter meaning beyond the schema.

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 states a specific verb and resource — splitting life cover into staggered-term policies to reduce cost — and points at an identical external calculator. It is clear about what is computed, but never contrasts itself with the sibling term_insurance_calculator, which an agent could easily confuse with this one.

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?

"Every input is optional; anything left out uses the default shown in its schema" is genuinely useful invocation guidance, telling the agent it can call the tool with no arguments at all. However, there is no statement of when this ladder approach applies versus a plain term-cover calculation, and no mention of the sibling that covers that case.

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