Skip to main content
Glama

BRAINIAC Insurance Underwriting & Policy Intelligence

Normalize loss runs

insurance-intelligence_loss-run-normalize

Normalize caller-supplied loss-run claim rows into paid/reserved/incurred fields. Not a claim adjudication. Price $0.04 USDC. POST /api/v1/insurance-intelligence/loss-run-normalize. Unpaid calls return 402 and do not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "insurance-intelligence_loss-run-normalize"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
asOfNo
fileNo
jsonNo
textNo
filesNo
limitsNo
lossRunsNo
policiesNo
premiumsNo
exclusionsNo
deductiblesNo
requirementsNo
evidenceItemsNo
requiredEvidenceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, this description does real work: it discloses price ($0.04 USDC), the payment gate ('unpaid calls return 402 and do not run'), and the POST endpoint. That is valuable operational context. It still omits what a successful response contains, whether normalization is idempotent, and how rows that fail to map are handled.

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?

Four short sentences, front-loaded with the action and scope negation before the commercial and transport details. No filler, though the telegraphic fragments ('Not a claim adjudication. Price $0.04 USDC.') read as notes rather than prose.

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 high-complexity tool with 15 nested parameters, no parameter descriptions, and no output schema, the description leaves most of the contract unstated. An agent cannot tell which of the many payload shapes to supply, how asOf interacts with loss runs, or what the normalized result looks like.

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 0% across 15 nested parameters, so the description must carry all parameter meaning and largely fails to. Only the paid/reserved/incurred targets are echoed; the dominant inputs (lossRuns, policies, limits, premiums, exclusions, deductibles, files/csv/json/text variants) and asOf are never explained or prioritized.

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 verb and resource ('Normalize caller-supplied loss-run claim rows') and states the target outputs (paid/reserved/incurred fields). The boundary 'Not a claim adjudication' helps separate it from judgement-producing tools, though it never names the closest sibling (policy-normalize) as an alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies the calling context: the caller already has loss-run claim rows and wants them mapped to canonical fields. The only explicit exclusion is 'not a claim adjudication'. There is no statement of when to prefer this over policy-normalize or the comparison tools, and no prerequisites for the input rows.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources