Skip to main content
Glama

Term Insurance Cover

term_insurance_calculator
Read-onlyIdempotent

How much life cover you need, worked out 3 ways. Same calculation as https://paisafinder.com/calculators/term-insurance-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_insurance_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageNoCurrent age (years)
goalsNoFuture goals (kids' edu, marriage) (rupees)
loansNoOutstanding loans (home/other) (rupees)
incomeNoAnnual income (rupees)
existingNoExisting life cover (rupees). Include employer group cover
retireAgeNoRetirement age (years)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 safety is covered. The description adds real context beyond that — the calculation mirrors a specific external calculator and omitted inputs silently fall back to schema defaults, meaning the agent gets a result even with zero arguments. It still does not explain the promised '3 ways' or what the response contains, so the added value is moderate.

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 with the purpose front-loaded and no filler. The 'worked out 3 ways' clause is the one piece that does not earn its place since it is never substantiated.

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?

For a pure, side-effect-free calculator with a fully documented schema and no output schema, the essentials for calling it are present. What is missing is the explanatory layer: which three methodologies are used and how outputs are structured, which matters for an agent deciding between this and the human life value calculator.

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%, with units (rupees, years), ranges and defaults all documented, so the baseline is 3. The description only reiterates the optional/default behavior already encoded in the schema and adds no calculation meaning, such as whether existing cover is subtracted from the total or how income is multiplied.

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 outcome (how much life cover you need) and ties it to a known reference implementation at paisafinder.com, so an agent can tell it computes required term cover rather than premiums. However, it never distinguishes itself from close siblings like human_life_value_calculator or health_insurance_cover_calculator, and the phrase 'worked out 3 ways' is never explained, leaving the actual computation ambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance, no when-not-to-use, and no mention of alternatives such as the human life value or policy ladder calculators. The only operative guidance is that all inputs are optional with defaults, which is invocation advice rather than selection advice.

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