Skip to main content
Glama
TurkActuary MCP

TurkActuary MCP

by afsharid

portfolio_metrics

Read-onlyIdempotent

Calculate frequency, severity, pure premium, and loss ratio for a consistent closed cohort using exposure, claim count, total loss, and earned premium.

Instructions

Tutarlı kapalı kohort için frekans, şiddet, saf prim ve hasar oranı.

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": {
      "exposure": "<exposure>",
      "claim_count": "<claim_count>",
      "total_loss": "<total_loss>",
      "earned_premium": "<earned_premium>"
    },
    "name": "portfolio_metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
exposureYesSonlu ondalık; oranlar yüzde değil (0.10 = %10).
total_lossYesSonlu ondalık; oranlar yüzde değil (0.10 = %10).
claim_countYes
earned_premiumYesSonlu 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
Behavior2/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 by structured data. The description adds nothing beyond that: it does not say how the four metrics are combined, how invalid or zero-exposure inputs are handled, or the shape of the returned result, and with no output schema that burden falls entirely on the description.

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?

A single short sentence with zero filler, and the scope constraint is front-loaded alongside the output list. It is efficient but borders on under-specification, since nothing in it explains the computation or its inputs.

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?

Listing the four computed quantities is the most important piece of context for a tool with no output schema, and that is present. Still missing for a four-required-parameter actuarial computation are the interaction between inputs (e.g. how exposure and claim_count yield frequency) and the returned structure, leaving the agent to infer the output shape.

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 75% and three of four parameters carry explicit notes about finite decimals and percent-vs-decimal conventions, so the schema does most of the work. The description adds no parameter meaning at all, not even clarifying the undocumented claim_count, which is the baseline 3 case rather than a value-add.

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 four concrete outputs (frequency, severity, pure premium, loss ratio) for a defined scope, a 'consistent closed cohort', so the resource is identifiable. However, there is no explicit verb (compute/return) and no differentiation from actuarially adjacent siblings such as combined_ratio or chain_ladder, which an agent could plausibly confuse with the loss-ratio output here.

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?

The phrase 'tutarlı kapalı kohort' implies a prerequisite (exposure and claims must come from a consistent closed cohort), which is mild scoping guidance. There is no statement of when to prefer this over combined_ratio, earned_exposure or the GLM tools, and no exclusions or preconditions spelled out.

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