Skip to main content
Glama

BRAINIAC Insurance Underwriting & Policy Intelligence

Detect coverage gaps

insurance-intelligence_coverage-gap-detect

Compare caller-supplied contract requirements to supplied limits, deductibles, and exclusions. Preliminary gap signals only—not coverage confirmation. Price $0.05 USDC. POST /api/v1/insurance-intelligence/coverage-gap-detect. 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_coverage-gap-detect"
  }
}

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.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose several operational traits: cost ($0.05 USDC), the POST endpoint, and that unpaid calls return 402 without running. It also caveats the output as preliminary. It stops short of stating input preconditions (e.g. that requirements plus at least one of limits/deductibles/exclusions are needed) or how the two sides are matched.

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?

Five short sentences, front-loaded with the core comparison before the caveat, price, endpoint, and payment-failure note. Nearly every sentence earns its place, though the raw endpoint path is arguably redundant with the tool name.

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 tool with 15 parameters, deep nested objects, no annotations, and no output schema, the description is thin: it never explains the left/right/prior/required side pairing, alternative input containers, or how evidence items are evaluated. It covers purpose, cost, and error behavior but leaves most of the calling surface undocumented.

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, so the description must compensate and largely fails to. It names only four concepts (requirements, limits, deductibles, exclusions) while leaving csv/text/json/file/files, asOf, lossRuns, policies, premiums, evidenceItems, requiredEvidence, and the pervasive 'side' enum entirely unexplained.

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 uses a specific verb and resource: 'Compare caller-supplied contract requirements to supplied limits, deductibles, and exclusions.' It is clear what the tool computes, but it makes no explicit reference to sibling tools (e.g. policy-limit-compare, policy-exclusion-compare) that an agent must choose between.

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?

The phrase 'Preliminary gap signals only—not coverage confirmation' usefully bounds the output's authority and implicitly tells the agent when not to rely on it for formal confirmation. However, there is no explicit guidance on when to choose this tool over the closely named siblings, nor any prerequisites for supplying requirement vs. limit data.

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