Skip to main content
Glama
TurkActuary MCP

TurkActuary MCP

by afsharid

life_insurance_pv

Read-onlyIdempotent

Calculates the present value of a term life insurance benefit paid at the end of the death period from mortality rates (qx), benefit amount, and interest rate.

Instructions

Verilen qx ile ölüm döneminin sonunda ödenen süreli hayat teminatı.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "qx": "<qx>",
      "benefit": "<benefit>",
      "rate": "<rate>"
    },
    "name": "life_insurance_pv"
  }
}

Input Schema

NameRequiredDescriptionDefault
qxYes
rateYesSonlu ondalık; oranlar yüzde değil (0.10 = %10).
benefitYesSonlu ondalık; oranlar yüzde değil (0.10 = %10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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 fully covered and the description need not repeat it. The description does add one genuine behavioral fact beyond the annotations: the benefit is paid at the END of the death period (end-of-year-of-death convention), which changes the formula versus a moment-of-death assumption. It says nothing about the interest/discount convention or the units of the returned value.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with no padding, which is structurally clean, but here the brevity is under-specification rather than economy. It does front-load the key input (qx) and the payment convention.

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?

A three-required-parameter closed-world calculation with no output schema needs the description to pin down the formula conventions and the meaning of the return value, and it does neither. The payment-timing note is the one piece of essential context supplied; the discounting basis and output units remain absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 67%, and all three parameter descriptions are the same boilerplate about finite decimals and percentages. The description only clarifies that qx carries the mortality rates; it never explains what "benefit" and "rate" mean in this actuarial context (sum assured versus discount/interest rate), so the ambiguous parameter is left unresolved in both schema and description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the object of computation ("süreli hayat teminatı" – term life benefit paid at the end of the death period given qx), but never states the action explicitly. A reader must infer from the tool name suffix "pv" that this computes a present value, and there is a sibling "life_annuity_pv" that the description does nothing to distinguish from.

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 guidance, no prerequisites, and no mention of alternatives such as life_annuity_pv or present_value. The agent is left to guess from the name alone whether this is the right tool for a death-benefit valuation versus an annuity valuation.

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