Coverage Cat

Auto insurance estimates

auto_estimates

Read-onlyIdempotent

Estimate monthly auto premiums for one driver and vehicle profile across several carriers. Returns each carrier's id, name, and monthly premium spread (lowest, lower, median, upper, and highest modeled premium) in US dollars, plus the normalized inputs the model used. These are model estimates for research, not bindable quotes.

Input Schema

Name	Required	Description
`age`	Yes	Age in years of the driver being priced; the model converts it to a birth year.
`zip`	Yes	ZIP code for the driver or garaging location being priced.
`make`	No	Vehicle manufacturer, such as `Toyota` or `Honda`.
`seed`	No	Optional deterministic seed for the estimate sample when a caller wants stable repeat runs.
`year`	No	Vehicle model year. With make and model it prices a specific car; omit it to price a generic vehicle instead.
`model`	No	Vehicle model, such as `Camry` or `Civic`.
`state`	Yes	Two-letter state code for the garaging address or rating state.
`style`	No	Vehicle trim, body style, or submodel when you want to narrow the vehicle match.
`gender`	Yes	Driver gender code the pricing model rates on: `M` for male, `F` for female, or `N` when not specified.
`collision_deductible`	No	Dollars the driver pays toward a collision repair before collision coverage pays the rest. Omitted means $1,000.
`comprehensive_deductible`	No	Dollars the driver pays toward non-collision damage, such as theft, hail, or vandalism, before comprehensive coverage pays the rest. Omitted means $1,000.

Output Schema

Name	Required	Description
`inputs`	Yes	Driver, vehicle, and deductible values the model used, with defaults filled in for omitted inputs.
`carriers`	Yes	One estimate per carrier the model could price.
`disclaimer`	Yes	Notice that these figures are informational estimates, not binding quotes; relay it with the numbers.
`estimate_unit`	Yes	Unit of the monthly premium spreads: `monthly_premium_usd`.

Schema Changelog

Changes observed during successful MCP inspections.

Changed17 schema fields changedOct 21, 2026

changedInput schema / properties / age / description

Previous value: -"Driver age for the quote scenario."New value: +"Age in years of the driver being priced; the model converts it to a birth year."

changedInput schema / properties / collision_deductible / description

Previous value: -"Collision deductible to use for the estimate scenario."New value: +"Dollars the driver pays toward a collision repair before collision coverage pays the rest. Omitted means $1,000."

changedInput schema / properties / comprehensive_deductible / description

Previous value: -"Comprehensive deductible to use for the estimate scenario."New value: +"Dollars the driver pays toward non-collision damage, such as theft, hail, or vandalism, before comprehensive coverage pays the rest. Omitted means $1,000."

changedInput schema / properties / gender / description

Previous value: -"Driver gender value used by the underlying pricing model."New value: +"Driver gender code the pricing model rates on: `M` for male, `F` for female, or `N` when not specified."

changedInput schema / properties / year / description

Previous value: -"Vehicle model year when you want the estimate to use a specific car."New value: +"Vehicle model year. With make and model it prices a specific car; omit it to price a generic vehicle instead."

addedOutput schema / properties / carriers / description

Added value: +"One estimate per carrier the model could price."

addedOutput schema / properties / carriers / items / properties / carrier / description
```
Added value: +"Carrier id, such as `geico`."
```

addedOutput schema / properties / carriers / items / properties / monthly / description

Added value: +"Modeled monthly premium spread for this carrier. Whole US dollars per month."

addedOutput schema / properties / carriers / items / properties / monthly / properties / lower / description
```
Added value: +"Lower end of the typical range."
```
addedOutput schema / properties / carriers / items / properties / monthly / properties / max / description
```
Added value: +"Highest modeled premium."
```
addedOutput schema / properties / carriers / items / properties / monthly / properties / median / description
```
Added value: +"Median modeled premium."
```
addedOutput schema / properties / carriers / items / properties / monthly / properties / min / description
```
Added value: +"Lowest modeled premium."
```
addedOutput schema / properties / carriers / items / properties / monthly / properties / upper / description
```
Added value: +"Upper end of the typical range."
```
addedOutput schema / properties / carriers / items / properties / name / description
```
Added value: +"Carrier display name."
```

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_unit / description

Added value: +"Unit of the monthly premium spreads: `monthly_premium_usd`."

addedOutput schema / properties / inputs / description

Added value: +"Driver, vehicle, and deductible values the model used, with defaults filled in for omitted inputs."

Changed12 schema fields changedOct 19, 2026

addedInput schema / properties / age / description

Added value: +"Driver age for the quote scenario."

addedInput schema / properties / collision_deductible / description

Added value: +"Collision deductible to use for the estimate scenario."

addedInput schema / properties / comprehensive_deductible / description

Added value: +"Comprehensive deductible to use for the estimate scenario."

addedInput schema / properties / gender / description

Added value: +"Driver gender value used by the underlying pricing model."

addedInput schema / properties / make / description

Added value: +"Vehicle manufacturer, such as `Toyota` or `Honda`."

addedInput schema / properties / model / description

Added value: +"Vehicle model, such as `Camry` or `Civic`."

addedInput schema / properties / seed / description

Added value: +"Optional deterministic seed for the estimate sample when a caller wants stable repeat runs."

addedInput schema / properties / state / description

Added value: +"Two-letter state code for the garaging address or rating state."

addedInput schema / properties / style / description

Added value: +"Vehicle trim, body style, or submodel when you want to narrow the vehicle match."

addedInput schema / properties / year / description

Added value: +"Vehicle model year when you want the estimate to use a specific car."

addedInput schema / properties / zip / description

Added value: +"ZIP code for the driver or garaging location being priced."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "carriers": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "carrier": {
+            "type": "string"
+          },
+          "monthly": {
+            "additionalProperties": false,
+            "properties": {
+              "lower": {
+                "type": "integer"
+              },
+              "max": {
+                "type": "integer"
+              },
+              "median": {
+                "type": "integer"
+              },
+              "min": {
+                "type": "integer"
+              },
+              "upper": {
+                "type": "integer"
+              }
+            },
+            "required": [
+              "min",
+              "lower",
+              "median",
+              "upper",
+              "max"
+            ],
+            "type": "object"
+          },
+          "name": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "carrier",
+          "name",
+          "monthly"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "disclaimer": {
+      "type": "string"
+    },
+    "estimate_unit": {
+      "type": "string"
+    },
+    "inputs": {
+      "additionalProperties": true,
+      "type": "object"
+    }
+  },
+  "required": [
+    "inputs",
+    "carriers",
+    "estimate_unit",
+    "disclaimer"
+  ],
+  "type": "object"
+}

First observedOct 17, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior. The description adds meaningful context beyond them: the returned fields (carrier id, name, five-point premium spread in USD, normalized inputs) and the critical caveat that results are model estimates, not bindable quotes. Rate limits, auth needs, and latency are not covered but are less relevant for a safe read-only estimator.

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?

Three compact sentences: purpose first, return shape second, research-only caveat third. Every sentence carries distinct information and nothing is repeated from the schema or annotations.

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

Completeness5/5

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

With 11 parameters, an output schema, and fully covering annotations, the description supplies the remaining decision-relevant facts: what the estimate covers, what comes back, and that it is not a bindable quote. Nothing needed to invoke it correctly is missing.

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 every parameter (including seed, deductibles, and vehicle fields) is already documented by the schema. The description adds no parameter-level detail beyond the schema, which is the correct baseline-3 case when the schema does the heavy lifting.

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?

States a specific verb and resource ('Estimate monthly auto premiums for one driver and vehicle profile across several carriers'), including scope (single profile, multiple carriers). This clearly separates it from sibling calculators like home_calculator and umbrella_calculator without needing to inspect schemas.

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?

Frames the tool as research-grade modeling ('model estimates for research, not bindable quotes'), which implicitly routes binding actions to siblings like homeowners_consumer_bind. However, it never explicitly names an alternative tool or states when-not-to-use conditions, so usage is clear but not fully enumerated.

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?