Skip to main content
Glama

BRAINIAC Insurance Underwriting & Policy Intelligence

Compare insurance programs

insurance-intelligence_program-comparison

Aggregate policy, limit, exclusion, deductible, premium, coverage-gap, and renewal comparisons from caller-supplied program records only. Price $0.08 USDC. POST /api/v1/insurance-intelligence/program-comparison. 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_program-comparison"
  }
}

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 still discloses two genuinely behavioral facts: the operation reads only caller-supplied records rather than fetching anything externally, and unpaid calls return 402 without executing. It does not address whether analysis is deterministic, how the many input modes interact, or what the caller gets back, leaving significant disclosure burden unmet for a complex tool.

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?

Three short sentences with the capability statement front-loaded, followed by the pricing/access constraints. No padding, though the raw HTTP route line adds little for an agent already given a 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 15-parameter nested-schema tool with no annotations and no output schema, the description covers only payment gating and data provenance. It omits how input modes are chosen, how sides are paired for comparison, and what the aggregate result contains, which are the questions an agent must resolve before calling it correctly.

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 deeply nested objects, so the description must compensate and it largely does not. It never explains the alternative input channels (csv/json/text/file/files), the meaning of asOf, or the critical side enum values (left/right/prior/renewal/current) that determine how records are paired for comparison.

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 names a specific verb (aggregate) and enumerates the comparison dimensions it covers (policy, limit, exclusion, deductible, premium, coverage-gap, renewal), which distinguishes it from the single-dimension siblings like policy-limit-compare. It does not name those siblings explicitly, so differentiation requires the agent to infer from the word 'aggregate', but the scope of the tool is clear.

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?

'Aggregate ... comparisons' and 'program records only' imply this is the full-program scan rather than a single-dimension check, which is usable implied guidance. However, there is no explicit when-to-use statement, no exclusions, and no routing to the narrower sibling tools when only one dimension matters.

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