Skip to main content
Glama
TurkActuary MCP

TurkActuary MCP

by afsharid

life_annuity_pv

Read-onlyIdempotent

Calculates the present value of a life-contingent term annuity from mortality rates (qx), payment amount, interest rate, and payment timing (immediate or due).

Instructions

Verilen qx ile yaşam koşullu süreli annüite (dönem sonu veya başı).

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>",
      "payment": "<payment>",
      "rate": "<rate>"
    },
    "name": "life_annuity_pv"
  }
}

Input Schema

NameRequiredDescriptionDefault
qxYes
rateYesSonlu ondalık; oranlar yüzde değil (0.10 = %10).
timingNo
paymentYesSonlu 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.4/5.0
Behavior1/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 fully covered. The description adds nothing beyond that: it does not disclose the return form (scalar vs array), the output unit/currency convention, what happens if qx length disagrees with the payment horizon, or any numerical failure modes.

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?

It is a single short sentence with no filler, and the key qualifier (given qx) is front-loaded. Its brevity borders on under-specification, but no sentence is wasted or redundant.

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

Completeness2/5

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

For a 4-parameter actuarial valuation function with no output schema and an undescribed enum, the description is too thin: it omits the return value, the convention that qx length sets the term, and the meaning/sign of 'payment' per period. An agent could guess the intent but not reliably call it correctly from the description alone.

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 50%: qx, rate and payment all share the same generic 'finite decimal, not percent' note, while the 'timing' enum has no schema description. The parenthetical '(dönem sonu veya başı)' partly compensates by mapping timing to end-of-period vs beginning-of-period, but the description never explains that qx is a mortality-rate vector whose length defines the term, nor how payment relates to each period.

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 names a specific actuarial resource ('yaşam koşullu süreli annüite' with given qx and end/beginning-of-period timing), so the object of computation is identifiable. However, it never states that the tool returns a present value (the 'pv' in the name carries that entirely) and it does not differentiate itself from close siblings such as 'annuity', 'life_insurance_pv' or 'present_value'.

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 mention of prerequisites, and no pointer to alternatives. The parenthetical '(dönem sonu veya başı)' hints at a modelling choice but does not tell the agent when that choice applies or which sibling to pick for an insurance/annuity variant instead.

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