Skip to main content
Glama

BRAINIAC Insurance Underwriting & Policy Intelligence

Normalize insurance policies

insurance-intelligence_policy-normalize

Normalize caller-supplied or locally extracted policy identity, term, and premium fields. Preliminary document analysis only—not coverage confirmation. Price $0.04 USDC. POST /api/v1/insurance-intelligence/policy-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_policy-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, the description carries the full burden. It does disclose valuable operational facts: paid endpoint at $0.04 USDC, HTTP path, and that unpaid calls return 402 and do not run. It omits what normalization actually produces, whether the operation is read-only, and any determinism or validation behavior.

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 purpose and immediately followed by the scope caveat and cost. The endpoint path and 402 note are terse and functional rather than padding.

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 15-parameter, deeply nested tool with no output schema and no annotations, the description is thin. An agent knows the price and endpoint but not the input contract or what comes back, which is a significant gap for a normalization tool whose output shape matters.

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 there are 15 parameters, several of which are nested arrays (limits, lossRuns, exclusions, deductibles, requirements, evidenceItems). The description only alludes to policy/premium fields and the file-or-text input choice; it explains nothing about the other payload collections or the 'side' enum semantics.

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?

States a specific verb and resource: normalize policy identity, term, and premium fields. The clause 'Preliminary document analysis only—not coverage confirmation' signals what the tool is not, which helps separate it from coverage-comparison siblings, though no sibling is named explicitly.

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?

Gives a usable context ('caller-supplied or locally extracted') and an implicit when-not ('not coverage confirmation'), but never names an alternative tool or states the condition that selects one sibling over another. An agent must infer routing from the sibling list.

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