Skip to main content
Glama

BRAINIAC Insurance Underwriting & Policy Intelligence

Check underwriting evidence completeness

insurance-intelligence_underwriting-evidence-completeness

Check caller-supplied evidence items against a required checklist. Missing items are flagged; coverage is not confirmed. Price $0.03 USDC. POST /api/v1/insurance-intelligence/underwriting-evidence-completeness. 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_underwriting-evidence-completeness"
  }
}

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, and it does disclose meaningful traits: pricing ($0.03 USDC), the 402 failure mode for unpaid calls, and the important limitation that coverage is not confirmed. However, it never states whether the operation is read-only or has side effects, and says nothing about response shape or limits on flagged items.

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?

The definition is short and front-loaded, leading with the action and its key caveat before pricing and payment mechanics. The endpoint path and per-sentence content are functional, though the raw POST path adds little for an agent that already selected the tool.

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?

This is a 15-parameter nested tool with no annotations and no output schema, so the description needs to do more. It never explains how the returned flags are shaped, how supplied evidence is matched against the required checklist, or what role the record-type arrays play in the check, leaving the agent unable to use most of the schema 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% across 15 parameters, many with nested objects, so the description must compensate and largely does not. 'Evidence items' and 'required checklist' loosely map to the evidenceItems and requiredEvidence arrays, but it never explains how they are matched (id, label, or category) or what the other thirteen parameters (csv, file, policies, limits, lossRuns, asOf, etc.) are for.

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 gives a specific verb and resource: it checks caller-supplied evidence items against a required checklist and flags missing ones. The scope caveat 'coverage is not confirmed' also separates it conceptually from coverage-gap-detect. It stops short of naming a sibling or stating the alternatives outright, so it is clear but not fully differentiated.

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?

Usage is implied: the agent can infer this is for auditing whether required evidence was supplied, and the 'coverage is not confirmed' line implies where to go for actual coverage analysis. There is no explicit when-to-use, when-not-to-use, or named alternative, and no stated prerequisites beyond payment.

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