Skip to main content
Glama

Human Life Value

human_life_value_calculator
Read-onlyIdempotent

Life cover based on what your future income is worth today. Same calculation as https://paisafinder.com/calculators/human-life-value-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": "human_life_value_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageNoCurrent age (years)
growthNoIncome growth p.a. (%). Long-term CPI+real growth ~6%
incomeNoAnnual income (rupees)
selfPctNoSelf-consumption (%). What you spend on yourself
discountNoDiscount rate (%). Risk-free G-Sec ~7%
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, non-destructive and closed-world, so the safety profile is covered. The description adds two genuinely useful behavioral facts beyond that: partial inputs are tolerated with schema defaults, and the exact reference implementation is pinned via URL so the agent can trust the output convention. It still says nothing about the shape or units of the result, which matters for a calculator with no output schema.

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 core concept, then the reference implementation, then the defaults rule; nothing is padded. The URL sentence is slightly gratuitous but it does add fidelity value for a deterministic calculator, so it earns its place.

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?

Annotations and a fully documented six-parameter schema are excellent, but with no output schema the description owes the agent at least a hint of what comes back (a single cover figure in rupees? a breakdown?) and its unit. It also lacks any positioning against the many insurance and retirement siblings, leaving a real gap for a tool this easy to mis-select.

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% — every one of the six parameters carries a description, default, bounds and even a rule of thumb (e.g. growth ~6% CPI+real, discount ~7% G-Sec). The description only restates that omitted inputs fall back to those schema defaults, adding no new meaning beyond the schema, so the baseline of 3 applies.

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 the resource concretely — life cover derived from the present value of future income — so an agent can tell this is a human-life-value insurance need calculation rather than a plain interest or tax tool. However, it uses no explicit verb ('calculates/computes') and never names a sibling, even though term_insurance_cover_calculator and health_insurance_cover_calculator sit in the same catalog and are easy to 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 Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance at all; the agent is not told how this differs from the term insurance or retirement calculators. The sentence about optional inputs is an invocation instruction (defaults), not tool-selection guidance, so usage must be inferred from the phrase 'life cover'.

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