Skip to main content
Glama

BRAINIAC Insurance Underwriting & Policy Intelligence

Detect insurance renewal changes

insurance-intelligence_renewal-change-detect

Detect insurer, premium, limit, and exclusion deltas between prior and renewal sides. Not insurer confirmation. Price $0.05 USDC. POST /api/v1/insurance-intelligence/renewal-change-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_renewal-change-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.2/5.0
Behavior3/5

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

With no annotations, the description does carry useful operational context: the $0.05 USDC price, the POST endpoint, and that unpaid calls return 402 without executing — genuine value for an unannotated tool. However, it says nothing about how prior/renewal sides are matched, whether results are computed deterministically, or how the many input modes (csv, text, json, file, files, typed arrays) interact, leaving significant behavioral gaps.

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?

Four short sentences, front-loaded with the payload description and followed by the constraint, price, and transport details. No padding, though the endpoint path and price are the kind of metadata that could sit in a reference field rather than the description body.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 deep nested objects and no output schema, the description should explain the input model and the shape of the delta result. It covers purpose and payment behavior but leaves the input-mode selection and side semantics undocumented, so an agent would need to guess on a fairly complex call.

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 it largely does not. The named categories (insurer, premium, limits, exclusions) hint at a few of the arrays, but the structured-input arrays for deductibles, loss runs, requirements, and evidence items, plus asOf and the prior/renewal side enums, are 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?

States a specific verb and resource — detecting deltas in insurer, premium, limit, and exclusion between prior and renewal sides — which is concrete and scoped. It also adds a negative disambiguation ("Not insurer confirmation"). It stops short of naming how it differs from close siblings such as premium-change-analyze, policy-limit-compare, or policy-exclusion-compare, so sibling separation is only partial.

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 definition implies usage through the prior-vs-renewal framing and rules out one adjacent use case (insurer confirmation). It never states when an agent should pick this over premium-change-analyze or policy-limit-compare, which cover overlapping field-level deltas, and gives no prerequisites or input-mode guidance.

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