Skip to main content
Glama
TurkActuary MCP

TurkActuary MCP

by afsharid

earned_exposure

Read-onlyIdempotent

Computes the portion of policy exposure earned during a chosen period from policy start and end dates, returning the result in years for actuarial calculations.

Instructions

Poliçe tarihlerinden dönem içinde kazanılmış maruziyet (yıl).

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": {
      "policies": "<policies>",
      "period_start": "<period_start>",
      "period_end": "<period_end>",
      "days_per_year": "<days_per_year>"
    },
    "name": "earned_exposure"
  }
}

Input Schema

NameRequiredDescriptionDefault
policiesYes
period_endYesYYYY-MM-DD
period_startYesYYYY-MM-DD
days_per_yearYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so safety is covered. The description adds nothing beyond them: it does not say how exposure is pro-rated across the period, whether the period must fall inside the policy terms, or how days_per_year affects the day-count convention.

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?

It is a single sentence with no filler, but it is terse to the point of under-specification, and the parenthetical '(yıl)' is the only hint about the return unit. Being short here trades away necessary meaning rather than eliminating waste.

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?

Four required parameters, nested policy objects, no output schema, and a calculation whose method matters (day-count convention, clipping to period boundaries). The description covers none of this, so an agent cannot predict the result or correct input shape from the definition alone.

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 only 50%: the three date parameters carry YYYY-MM-DD descriptions, but days_per_year has no description beyond a 360-366 range, and the description does not explain that it selects the day-count basis (360 vs 365). Nothing is said about what the policies array entries mean (start/end coverage intervals) or whether periods outside them yield zero exposure.

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 quantity (earned exposure, in years) and its inputs (policy dates, period), so the agent knows roughly what is computed. However, it is a single compressed phrase that never states the operation explicitly (calculate/sum) nor distinguishes it from sibling calculations such as annuity 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 prerequisites, and no mention of any alternative tool. An agent must infer entirely from the duty title that this is the pro-rata exposure calculator rather than a pricing or reserving function.

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