Coverage Cat

Auto claim filing break-even calculator

file_a_claim

Read-onlyIdempotent

Estimate whether filing an auto collision claim costs more than paying for the repair yourself. Returns monthly premium spreads with and without one claim, the monthly and multi-year premium increase, the collision deductible, the total cost of filing (deductible plus premium increase), and a file_claim or pay_out_of_pocket recommendation with the estimated savings. These are model estimates, not carrier 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.
`repair_estimate`	Yes	Approximate dollar amount you expect to pay to repair the vehicle if you do not file a claim.
`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.
`deductible`	Yes	Collision deductible paid when filing.
`disclaimer`	Yes	Notice that these figures are informational estimates, not binding quotes; relay it with the numbers.
`claim_monthly`	Yes	Monthly premium spread after filing one claim. Whole US dollars per month.
`estimate_unit`	Yes	Currency of every dollar figure: `usd`.
`recommendation`	No	Whether filing or paying out of pocket costs less; null when no repair estimate was read.
`repair_estimate`	Yes	The repair estimate you sent.
`monthly_increase`	Yes	Median monthly premium increase after the claim.
`no_claim_monthly`	Yes	Monthly premium spread with no claim on record. Whole US dollars per month.
`premium_increase`	Yes	Total extra premium over premium_impact_years.
`total_claim_cost`	Yes	Total cost of filing: deductible plus premium_increase.
`premium_impact_years`	Yes	Years the higher premium is assumed to last.

Schema Changelog

Changes observed during successful MCP inspections.

Changed29 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 / claim_monthly / description

Added value: +"Monthly premium spread after filing one claim. Whole US dollars per month."

addedOutput schema / properties / claim_monthly / properties / lower / description
```
Added value: +"Lower end of the typical range."
```
addedOutput schema / properties / claim_monthly / properties / max / description
```
Added value: +"Highest modeled premium."
```
addedOutput schema / properties / claim_monthly / properties / median / description
```
Added value: +"Median modeled premium."
```
addedOutput schema / properties / claim_monthly / properties / min / description
```
Added value: +"Lowest modeled premium."
```
addedOutput schema / properties / claim_monthly / properties / upper / description
```
Added value: +"Upper end of the typical range."
```
addedOutput schema / properties / deductible / description
```
Added value: +"Collision deductible paid when filing."
```

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: +"Currency of every dollar figure: `usd`."
```

addedOutput schema / properties / inputs / description

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

addedOutput schema / properties / monthly_increase / description

Added value: +"Median monthly premium increase after the claim."

addedOutput schema / properties / no_claim_monthly / description

Added value: +"Monthly premium spread with no claim on record. Whole US dollars per month."

addedOutput schema / properties / no_claim_monthly / properties / lower / description
```
Added value: +"Lower end of the typical range."
```
addedOutput schema / properties / no_claim_monthly / properties / max / description
```
Added value: +"Highest modeled premium."
```
addedOutput schema / properties / no_claim_monthly / properties / median / description
```
Added value: +"Median modeled premium."
```
addedOutput schema / properties / no_claim_monthly / properties / min / description
```
Added value: +"Lowest modeled premium."
```
addedOutput schema / properties / no_claim_monthly / properties / upper / description
```
Added value: +"Upper end of the typical range."
```
addedOutput schema / properties / premium_impact_years / description
```
Added value: +"Years the higher premium is assumed to last."
```

addedOutput schema / properties / premium_increase / description

Added value: +"Total extra premium over premium_impact_years."

addedOutput schema / properties / recommendation / description

Added value: +"Whether filing or paying out of pocket costs less; null when no repair estimate was read."

addedOutput schema / properties / recommendation / properties / action / description

Added value: +"`file_claim` when repair_estimate exceeds total_claim_cost, otherwise `pay_out_of_pocket`."

addedOutput schema / properties / recommendation / properties / estimated_savings / description
```
Added value: +"Dollars saved by taking action instead of the alternative."
```
addedOutput schema / properties / repair_estimate / description
```
Added value: +"The repair estimate you sent."
```

addedOutput schema / properties / total_claim_cost / description

Added value: +"Total cost of filing: deductible plus premium_increase."

Changed13 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 / repair_estimate / description

Added value: +"Approximate dollar amount you expect to pay to repair the vehicle if you do not file a claim."

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": {
+    "claim_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"
+    },
+    "deductible": {
+      "type": "integer"
+    },
+    "disclaimer": {
+      "type": "string"
+    },
+    "estimate_unit": {
+      "type": "string"
+    },
+    "inputs": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "monthly_increase": {
+      "type": "integer"
+    },
+    "no_claim_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"
+    },
+    "premium_impact_years": {
+      "type": "integer"
+    },
+    "premium_increase": {
+      "type": "integer"
+    },
+    "recommendation": {
+      "additionalProperties": false,
+      "properties": {
+        "action": {
+          "type": "string"
+        },
+        "estimated_savings": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "action",
+        "estimated_savings"
+      ],
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "repair_estimate": {
+      "type": "integer"
+    },
+    "total_claim_cost": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "inputs",
+    "no_claim_monthly",
+    "claim_monthly",
+    "monthly_increase",
+    "premium_impact_years",
+    "premium_increase",
+    "deductible",
+    "total_claim_cost",
+    "repair_estimate",
+    "estimate_unit",
+    "disclaimer"
+  ],
+  "type": "object"
+}

First observedOct 17, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds a meaningful accuracy caveat ('model estimates, not carrier quotes') that tells the agent how much to trust the output. It stops short of describing determinism (the seed param) or the sampling behavior.

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?

Front-loaded with the decision question, followed by a compact enumeration of returns and the estimate caveat. The return-value listing is somewhat verbose given an output schema exists, but nothing is wasted or confusing.

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 a read-only calculation tool with full annotation coverage and a present output schema, the description covers purpose, returns, and an accuracy disclaimer. The main gap is the absence of routing guidance to sibling estimation tools.

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 coverage is 100%, so all 12 parameters are already documented in the schema. The description only alludes to the collision deductible and offers no additional parameter semantics beyond what the schema provides, so the baseline 3 applies.

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 decision ('Estimate whether filing an auto collision claim costs more than paying for the repair yourself'), clearly distinguishing this break-even calculator from the generic auto_estimates sibling, though it does not name that sibling explicitly.

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 purpose implies when to use it (a claim-vs-pay decision), but there is no explicit when-to-use guidance or reference to alternatives such as auto_estimates or collision_and_comprehensive_coverage. Usage is inferable but not spelled out.

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?