Coverage Cat

Umbrella insurance calculator

umbrella_calculator

Read-onlyIdempotent

Research-only estimate of annual personal umbrella pricing bands, the inferred risk class, and per-factor impacts for directional pricing. Use this for price exploration, not when the shopper wants Coverage Cat to shop for or buy umbrella insurance.

Input Schema

Name	Required	Description
`zip`	Yes	ZIP code for the household being priced.
`jet_skis`	No	Count of personal watercraft such as jet skis.
`auto_count`	No	How many cars, trucks, or SUVs are in the household auto profile.
`motorcycles`	No	How many motorcycles should be added to the total vehicle exposure.
`property_count`	No	How many residential properties the household owns or carries liability for.
`drivers_over_70`	No	Number of drivers in the household who are 70 or older.
`antique_vehicles`	No	How many collector or antique vehicles should be counted in the risk profile.
`drivers_under_22`	No	Number of drivers in the household who are younger than 22.
`large_watercraft`	No	Count of boats of any size; personal watercraft go under jet_skis.
`moving_violations`	No	Total moving violations across all household drivers. Omitted counts as none; a high count can move the profile to specialized review or make it ineligible for instant pricing.
`at_fault_accidents`	No	Total at-fault accidents across all household drivers. Omitted counts as none; a high count can move the profile to specialized review or make it ineligible for instant pricing.

Output Schema

Name	Required	Description
`inputs`	Yes	The household counts you sent, parsed to integers; omitted counts are left out.
`estimate`	Yes	Risk class and annual premium bands.
`disclaimer`	Yes	Notice that these figures are informational estimates, not binding quotes; relay it with the numbers.
`estimate_unit`	Yes	Unit of every price: `annual_premium_usd`, annual premium in US dollars.
`factor_impacts`	Yes	Household factors that moved the profile off the best (`preferred`) class; empty when none did.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026

changedInput schema / properties / large_watercraft / description

Previous value: -"Count of boats or other large watercraft that add umbrella liability exposure."New value: +"Count of boats of any size; personal watercraft go under jet_skis."

Changed18 schema fields changedOct 21, 2026

changedInput schema / properties / at_fault_accidents / description

Previous value: -"Recent at-fault accidents that should be reflected in the umbrella risk profile."New value: +"Total at-fault accidents across all household drivers. Omitted counts as none; a high count can move the profile to specialized review or make it ineligible for instant pricing."

changedInput schema / properties / moving_violations / description

Previous value: -"Recent moving violations that should be reflected in the umbrella risk profile."New value: +"Total moving violations across all household drivers. Omitted counts as none; a high count can move the profile to specialized review or make it ineligible for instant pricing."

addedOutput schema / properties / disclaimer / description

Added value: +"Notice that these figures are informational estimates, not binding quotes; relay it with the numbers."

addedOutput schema / properties / estimate / description
```
Added value: +"Risk class and annual premium bands."
```

addedOutput schema / properties / estimate / properties / class / description

Added value: +"Risk class inferred from the household profile, such as `preferred` or `standard`."

addedOutput schema / properties / estimate / properties / prices / description

Added value: +"One annual premium band per umbrella limit available in the state."

addedOutput schema / properties / estimate / properties / prices / items / properties / coverage_millions / description
```
Added value: +"Umbrella limit in millions of dollars."
```
addedOutput schema / properties / estimate / properties / prices / items / properties / high / description
```
Added value: +"High end of the annual premium band."
```
addedOutput schema / properties / estimate / properties / prices / items / properties / low / description
```
Added value: +"Low end of the annual premium band."
```
addedOutput schema / properties / estimate / properties / prices / items / properties / mid / description
```
Added value: +"Typical annual premium."
```

addedOutput schema / properties / estimate / properties / umbrella_class / description

Added value: +"Class used for pricing; it adds `_with_youth` to a standard class when any driver is under 22."

addedOutput schema / properties / estimate_unit / description

Added value: +"Unit of every price: `annual_premium_usd`, annual premium in US dollars."

addedOutput schema / properties / factor_impacts / description

Added value: +"Household factors that moved the profile off the best (`preferred`) class; empty when none did."

addedOutput schema / properties / factor_impacts / items / properties / factor / description
```
Added value: +"Internal factor id, such as `moving_violation_count`."
```
addedOutput schema / properties / factor_impacts / items / properties / impact / description
```
Added value: +"Class this factor alone puts the profile in."
```
addedOutput schema / properties / factor_impacts / items / properties / label / description
```
Added value: +"Shopper-facing name of the factor."
```
addedOutput schema / properties / factor_impacts / items / properties / value / description
```
Added value: +"Count the estimate used for this factor."
```

addedOutput schema / properties / inputs / description

Added value: +"The household counts you sent, parsed to integers; omitted counts are left out."

Changed12 schema fields changedOct 19, 2026

addedInput schema / properties / antique_vehicles / description

Added value: +"How many collector or antique vehicles should be counted in the risk profile."

addedInput schema / properties / at_fault_accidents / description

Added value: +"Recent at-fault accidents that should be reflected in the umbrella risk profile."

addedInput schema / properties / auto_count / description

Added value: +"How many cars, trucks, or SUVs are in the household auto profile."

addedInput schema / properties / drivers_over_70 / description

Added value: +"Number of drivers in the household who are 70 or older."

addedInput schema / properties / drivers_under_22 / description

Added value: +"Number of drivers in the household who are younger than 22."

addedInput schema / properties / jet_skis / description

Added value: +"Count of personal watercraft such as jet skis."

addedInput schema / properties / large_watercraft / description

Added value: +"Count of boats or other large watercraft that add umbrella liability exposure."

addedInput schema / properties / motorcycles / description

Added value: +"How many motorcycles should be added to the total vehicle exposure."

addedInput schema / properties / moving_violations / description

Added value: +"Recent moving violations that should be reflected in the umbrella risk profile."

addedInput schema / properties / property_count / description

Added value: +"How many residential properties the household owns or carries liability for."

changedInput schema / properties / zip / description

Previous value: -"Five-digit ZIP code."New value: +"ZIP code for the household being priced."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "disclaimer": {
+      "type": "string"
+    },
+    "estimate": {
+      "additionalProperties": false,
+      "properties": {
+        "class": {
+          "type": "string"
+        },
+        "prices": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "coverage_millions": {
+                "type": "integer"
+              },
+              "high": {
+                "type": "integer"
+              },
+              "low": {
+                "type": "integer"
+              },
+              "mid": {
+                "type": "integer"
+              }
+            },
+            "required": [
+              "coverage_millions",
+              "low",
+              "mid",
+              "high"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "umbrella_class": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "class",
+        "umbrella_class",
+        "prices"
+      ],
+      "type": "object"
+    },
+    "estimate_unit": {
+      "type": "string"
+    },
+    "factor_impacts": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "factor": {
+            "type": "string"
+          },
+          "impact": {
+            "type": "string"
+          },
+          "label": {
+            "type": "string"
+          },
+          "value": {
+            "type": "integer"
+          }
+        },
+        "required": [
+          "factor",
+          "label",
+          "value",
+          "impact"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "inputs": {
+      "additionalProperties": true,
+      "type": "object"
+    }
+  },
+  "required": [
+    "inputs",
+    "estimate",
+    "factor_impacts",
+    "estimate_unit",
+    "disclaimer"
+  ],
+  "type": "object"
+}

First observedOct 17, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds useful context that this is a research-only directional estimate rather than a binding quote or purchase action, though it does not discuss auth, limits, or detailed eligibility behavior.

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 two sentences and front-loads what the tool returns before stating the usage boundary. Every sentence contributes directly to selection or correct use.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter estimate with an output schema and rich annotations, the description covers purpose, output nature, and the key usage boundary. It could say more about estimate limitations or eligibility implications, but the schema and output schema carry the detailed parameter and return-value information.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all 11 parameters are already documented in the schema. The description only implies that those factors drive risk class and per-factor impacts; it adds no parameter syntax, defaults, or special-case guidance beyond the schema.

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: an estimate of annual personal umbrella pricing bands, inferred risk class, and per-factor impacts. It also distinguishes this research-only pricing tool from the shop/buy umbrella sibling tools.

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?

It gives an explicit when-to-use case (price exploration) and a when-not case (when the shopper wants Coverage Cat to shop for or buy umbrella insurance). It does not name the specific alternative consumer/shop tools, so the routing is clear but not fully explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Coverage Cat tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?