Skip to main content
Glama

BRAINIAC Insurance Underwriting & Policy Intelligence

Analyze premium changes

insurance-intelligence_premium-change-analyze

Analyze prior versus renewal premium amounts from caller-supplied policy or premium rows. Price $0.03 USDC. POST /api/v1/insurance-intelligence/premium-change-analyze. 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_premium-change-analyze"
  }
}

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

C2.9/5.0
Behavior3/5

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

With zero annotations the description carries the full burden, and it does disclose genuinely useful, non-obvious behavior: a $0.03 USDC price, the POST route, and that unpaid calls return 402 and do not execute. That payment-failure contract is valuable. However it says nothing about how prior vs renewal rows are matched, what happens with ambiguous or missing sides, or what the response contains — significant gaps for a 15-parameter analytical 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?

Four short sentences, each doing distinct work: purpose, price, endpoint, payment failure behavior. The purpose is front-loaded and there is no filler. It could arguably fold the endpoint and price into one line, but nothing 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 tool this complex — 15 top-level params, nested objects, no output schema, no annotations — the description is thin. It omits how inputs are structured (single payload vs prior/renewal sides), what the analysis returns, and how 'side' should be assigned. The payment disclosure is helpful but insufficient for correct invocation.

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 nested arrays for policies, premiums, limits, lossRuns, exclusions, deductibles, requirements, and evidence. The description only alludes to 'policy or premium rows', leaving the meaning of asOf, csv/json/text/files, and especially the recurring 'side' enum (prior/renewal/required etc.) 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?

The description opens with a specific verb+resource: 'Analyze prior versus renewal premium amounts from caller-supplied policy or premium rows.' This tells an agent exactly what comparison is performed and what input feeds it. It doesn't distinguish itself from siblings like renewal-change-detect, but the purpose is unambiguous on its own.

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

Usage Guidelines2/5

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

There is no when-to-use versus when-not guidance; the description never names an alternative or a condition that selects this tool over renewal-change-detect or program-comparison. Input source ('caller-supplied policy or premium rows') hints at context but is not selection 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