Skip to main content
Glama
TurkActuary MCP

TurkActuary MCP

by afsharid

gamma_severity_glm

Read-onlyIdempotent

Fits a claim-count-weighted gamma GLM with a log link to model claim severity across categorical factors.

Instructions

Hasar adediyle ağırlıklı log bağlantılı gamma şiddet GLM'i (kategorik faktörler).

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": {
      "rows": "<rows>",
      "factors": "<factors>"
    },
    "name": "gamma_severity_glm"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes
factorsYes
base_levelsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is covered. The description adds that fitting is claim-count weighted with a log link, which is genuine methodological context, but says nothing about failure behavior (non-convergence, invalid factors), output/results shape, or limits despite rows being capped at 2000. That is adequate, not rich.

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 compact sentence with the method, link function, weighting and scope front-loaded, and no filler. It is efficient, though the brevity comes partly at the cost of the guidance the other dimensions penalize.

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 three-parameter tool with nested input objects, a capped row count and no output schema, the description is too thin: it never clarifies what base_levels does, how rows must be pre-aggregated, or what the agent receives back. An agent could construct a call from the schema, but not confidently.

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 0% and the schema has three parameters including nested objects, so the description must compensate and largely does not. 'Kategorik faktörler' loosely gestures at the factors array, but rows (with levels/claims/total_loss) and especially the optional base_levels reference-level map are never explained, leaving an agent to infer their meaning from the schema alone.

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?

Names a specific statistical method and resource: a gamma severity GLM with log link, claim-count weighted, for categorical factors. This is far more specific than a generic 'fit model', and the 'severity' framing implicitly distinguishes it from the frequency-oriented poisson_glm sibling, though that contrast is never stated explicitly.

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 statement of when to use this tool, when not to, or what the alternative is. An agent facing poisson_glm versus gamma_severity_glm gets no routing help beyond the word 'severity'; prerequisites (e.g. that data must be aggregated to claim-count and loss levels) are absent.

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