Skip to main content
Glama
TurkActuary MCP

TurkActuary MCP

by afsharid

poisson_glm

Read-onlyIdempotent

Fit a log-linked Poisson GLM with exposure offset to model claim frequency and estimate relative coefficients across categorical rating factors.

Instructions

Maruziyet ofsetli log bağlantılı Poisson frekans GLM'i (kategorik faktörler, göreli katsayılar).

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": "poisson_glm"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes
factorsYes
base_levelsNo

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?

The 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 how the model is specified (offset plus log link), but says nothing about output form, how base levels are handled, or how failures such as singular designs are reported.

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 dense sentence whose parenthetical carries real information (categorical factors and relative rather than absolute coefficients), with the key qualifier, exposure offset, stated up front. Nothing is wasted, though the terseness leaves no room for the missing operational guidance.

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 a nested rows array, a factors list and a base_levels map, no output schema and no parameter documentation, this one-sentence description is not enough. An agent can tell it fits a frequency GLM, but not what shape its results take or how to structure the nested input.

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%: rows, factors and base_levels are all documented only by their types, and the nested levels object and its string-valued additionalProperties are entirely unexplained. The description hints that factors are categorical and results are relative, but it does not explain the reference-category role of base_levels or the units of exposure, which the schema alone only partly covers.

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 technique and resource: a Poisson frequency GLM with log link and exposure offset, restricted to categorical factors and reporting relative coefficients. That is enough to separate it from gamma_severity_glm and the other actuarial siblings, though it does not name an alternative 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?

It states what the model is but never says when to choose it over siblings such as gamma_severity_glm or credibility_estimate, nor what data preconditions must hold (for example, non-negative integer claims and positive exposure). Usage must be inferred from the method name alone.

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