Skip to main content
Glama

BRAINIAC Insurance Underwriting & Policy Intelligence

Compare policy limits

insurance-intelligence_policy-limit-compare

Compare caller-supplied left/right or prior/renewal coverage limits. Not a coverage determination. Price $0.04 USDC. POST /api/v1/insurance-intelligence/policy-limit-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-limit-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

B3.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries full behavioral burden. It discloses valuable operational facts: price ($0.04 USDC), a payment gate (unpaid calls return 402 and do not run), and the POST endpoint. But it omits read-only vs mutating nature, what the comparison returns, and the shape of results, which is a significant gap for a complex tool with no annotations or output schema.

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, front-loaded sentences. Purpose comes first, then scope caveat, price, endpoint, and failure behavior. Minimal waste; each sentence adds practical information.

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 tool with deeply nested objects, no annotations, and no output schema, the description is too thin. It doesn't explain how to supply input (which channels or structures are needed) or what output to expect, leaving the agent under-equipped to invoke 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 nested parameters. The description only alludes to the 'side' concept via left/right/prior/renewal, leaving the many input channels (csv, text, json, file, files) and data structures (limits, lossRuns, deductibles, requirements) entirely unexplained. It does not compensate for the coverage gap.

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 (compare) and resource (coverage limits) with the scope qualifier 'caller-supplied left/right or prior/renewal'. The clause 'Not a coverage determination' helps rule out siblings like coverage-gap-detect. Clear but doesn't name a specific alternative tool.

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 'left/right or prior/renewal' phrasing implies the two comparison modes, and 'Not a coverage determination' serves as an implicit when-not hint. However, no explicit when-to-use guidance or named alternative is given, leaving selection partly to inference.

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