Skip to main content
Glama
TurkActuary MCP

TurkActuary MCP

by afsharid

life_cashflow_projection

Read-onlyIdempotent

Projects periodic life insurance cash flows and present values using mortality, lapse, premium, benefit, surrender, and expense data for valuation and reserving.

Instructions

Ölüm ve iptal çıkışlı dönemlik hayat poliçesi nakit akışı ve bugünkü değerler.

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>",
      "rate": "<rate>",
      "premium": "<premium>",
      "death_benefit": "<death_benefit>"
    },
    "name": "life_cashflow_projection"
  }
}

Input Schema

NameRequiredDescriptionDefault
qxYes
rateYesSonlu ondalık; oranlar yüzde değil (0.10 = %10).
lapseNo
premiumYesSonlu ondalık; oranlar yüzde değil (0.10 = %10).
death_benefitYesSonlu ondalık; oranlar yüzde değil (0.10 = %10).
surrender_valueNo
maturity_benefitNoSonlu ondalık; oranlar yüzde değil (0.10 = %10).
expense_per_policyNoSonlu 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.6/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds nothing beyond the purpose: it does not state timing conventions for cash flows, how omitted optional inputs (lapse, surrender_value, maturity_benefit) are treated, or what the returned structure looks like.

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 front-loaded sentence with no filler, but it errs toward under-specification rather than tightness — the brevity leaves required modeling assumptions unstated.

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 an 8-parameter actuarial projection with no output schema, the definition should convey array alignment, default handling for the four optional decrement/benefit inputs, and at least a hint of the cash-flow output shape. Mentioning 'cash flow and present values' is a start but far from sufficient.

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 coverage is 63%, and the embedded parameter descriptions are identical boilerplate ('finite decimal; rates not percentages'), which does not explain the semantics of qx versus lapse versus surrender_value arrays. The description does not clarify the critical constraint that these arrays must align by policy duration or that qx length likely sets the projection horizon.

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 names a specific computation: periodic cash flow for a life policy with death and lapse decrements, plus present values. That is more precise than a bare 'life insurance PV' sibling, though it does not explicitly differentiate itself from life_annuity_pv, 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 statement of prerequisites, and no routing to the PV-only siblings for simpler cases. The agent must infer from the name alone when this projection is preferable to the other life/present-value tools.

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