Skip to main content
Glama

BRAINIAC Insurance Underwriting & Policy Intelligence

Compare policy exclusions

insurance-intelligence_policy-exclusion-compare

Compare caller-supplied exclusion schedules across prior/renewal or left/right sides. Preliminary text matching only. Price $0.04 USDC. POST /api/v1/insurance-intelligence/policy-exclusion-compare. 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-exclusion-compare"
  }
}

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

A3.7/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 behavioral burden. It usefully discloses the $0.04 USDC price, the POST endpoint, the 402 response for unpaid calls, and that matching is preliminary text matching only. However, it does not explain output shape, matching logic, side-mapping behavior, or limitations for complex inputs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core comparison purpose and side labels. Payment and endpoint details are compact and operationally relevant, and no sentence is redundant.

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 complex tool with 15 parameters, nested objects, many payload arrays, no output schema, and no annotations, the description is far too thin. It omits input guidance for most parameters and does not explain the response structure or comparison behavior beyond the preliminary text-matching caveat.

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, including many nested arrays and file/CSV/text payload options. The description explains only the side concepts (prior/renewal, left/right) and does not document the roles of csv, json, text, file, files, exclusions, limits, lossRuns, policies, or other arrays.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: compare exclusion schedules. It also defines the comparison sides (prior/renewal or left/right) and labels the operation as preliminary text matching, which clearly distinguishes it from siblings such as policy-limit-compare or coverage-gap-detect.

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

Usage Guidelines4/5

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

The description clearly establishes the tool's context: compare caller-supplied exclusion schedules across renewal/prior or left/right sides. It also notes the matching is text-only and preliminary. It does not explicitly say when to choose this over alternatives or discuss exclusions, so it falls short of the highest tier.

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