Skip to main content
Glama

Coverage Cat

Collision and comprehensive coverage calculator

collision_and_comprehensive_coverage
Read-onlyIdempotent

Estimate what collision and comprehensive coverage cost for one driver and vehicle profile, to help decide whether to carry them. Returns monthly premium spreads in US dollars with no physical-damage coverage, collision only, and both, plus collision-only and both after one claim, and cumulative premium projections for each coverage option over projection_years. These are model estimates, not bindable quotes.

Input Schema

NameRequiredDescriptionDefault
ageYesAge in years of the driver being priced; the model converts it to a birth year.
zipYesZIP code for the driver or garaging location being priced.
makeNoVehicle manufacturer, such as `Toyota` or `Honda`.
seedNoOptional deterministic seed for the estimate sample when a caller wants stable repeat runs.
yearNoVehicle model year. With make and model it prices a specific car; omit it to price a generic vehicle instead.
modelNoVehicle model, such as `Camry` or `Civic`.
stateYesTwo-letter state code for the garaging address or rating state.
styleNoVehicle trim, body style, or submodel when you want to narrow the vehicle match.
genderYesDriver gender code the pricing model rates on: `M` for male, `F` for female, or `N` when not specified.
collision_deductibleNoDollars the driver pays toward a collision repair before collision coverage pays the rest. Omitted means $1,000.
comprehensive_deductibleNoDollars 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

NameRequiredDescriptionDefault
inputsYesDriver, vehicle, and deductible values the model used, with defaults filled in for omitted inputs.
disclaimerYesNotice that these figures are informational estimates, not binding quotes; relay it with the numbers.
estimate_unitYesUnit of the monthly premium spreads: `monthly_premium_usd`.
projection_yearsYesNumber of years the cumulative projections cover.
monthly_estimatesYesMonthly premium spread for each coverage scenario.
cumulative_annual_scenariosYesRunning premium totals for the without, collision-only, and both coverage options.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed44 schema fields changed
    • 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 / cumulative_annual_scenarios / description
      Added value: +"Running premium totals for the without, collision-only, and both coverage options."
    • addedOutput schema / properties / cumulative_annual_scenarios / items / properties / cumulative_annual_premiums / description
      Added value: +"Total premium in US dollars paid by the end of each year from 1 to projection_years, based on the median monthly premium."
    • addedOutput schema / properties / cumulative_annual_scenarios / items / properties / label / description
      Added value: +"Shopper-facing scenario name."
    • addedOutput schema / properties / cumulative_annual_scenarios / items / properties / scenario / description
      Added value: +"Scenario key in monthly_estimates: `without`, `collision`, or `both`."
    • 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."
    • addedOutput schema / properties / monthly_estimates / description
      Added value: +"Monthly premium spread for each coverage scenario."
    • addedOutput schema / properties / monthly_estimates / properties / both / description
      Added value: +"With collision and comprehensive coverage. Whole US dollars per month."
    • addedOutput schema / properties / monthly_estimates / properties / both / properties / lower / description
      Added value: +"Lower end of the typical range."
    • addedOutput schema / properties / monthly_estimates / properties / both / properties / max / description
      Added value: +"Highest modeled premium."
    • addedOutput schema / properties / monthly_estimates / properties / both / properties / median / description
      Added value: +"Median modeled premium."
    • addedOutput schema / properties / monthly_estimates / properties / both / properties / min / description
      Added value: +"Lowest modeled premium."
    • addedOutput schema / properties / monthly_estimates / properties / both / properties / upper / description
      Added value: +"Upper end of the typical range."
    • addedOutput schema / properties / monthly_estimates / properties / both_claim / description
      Added value: +"With collision and comprehensive coverage, after one claim. Whole US dollars per month."
    • addedOutput schema / properties / monthly_estimates / properties / both_claim / properties / lower / description
      Added value: +"Lower end of the typical range."
    • addedOutput schema / properties / monthly_estimates / properties / both_claim / properties / max / description
      Added value: +"Highest modeled premium."
    • addedOutput schema / properties / monthly_estimates / properties / both_claim / properties / median / description
      Added value: +"Median modeled premium."
    • addedOutput schema / properties / monthly_estimates / properties / both_claim / properties / min / description
      Added value: +"Lowest modeled premium."
    • addedOutput schema / properties / monthly_estimates / properties / both_claim / properties / upper / description
      Added value: +"Upper end of the typical range."
    • addedOutput schema / properties / monthly_estimates / properties / collision / description
      Added value: +"With collision coverage only. Whole US dollars per month."
    • addedOutput schema / properties / monthly_estimates / properties / collision / properties / lower / description
      Added value: +"Lower end of the typical range."
    • addedOutput schema / properties / monthly_estimates / properties / collision / properties / max / description
      Added value: +"Highest modeled premium."
    • addedOutput schema / properties / monthly_estimates / properties / collision / properties / median / description
      Added value: +"Median modeled premium."
    • addedOutput schema / properties / monthly_estimates / properties / collision / properties / min / description
      Added value: +"Lowest modeled premium."
    • addedOutput schema / properties / monthly_estimates / properties / collision / properties / upper / description
      Added value: +"Upper end of the typical range."
    • addedOutput schema / properties / monthly_estimates / properties / collision_claim / description
      Added value: +"With collision coverage only, after one claim. Whole US dollars per month."
    • addedOutput schema / properties / monthly_estimates / properties / collision_claim / properties / lower / description
      Added value: +"Lower end of the typical range."
    • addedOutput schema / properties / monthly_estimates / properties / collision_claim / properties / max / description
      Added value: +"Highest modeled premium."
    • addedOutput schema / properties / monthly_estimates / properties / collision_claim / properties / median / description
      Added value: +"Median modeled premium."
    • addedOutput schema / properties / monthly_estimates / properties / collision_claim / properties / min / description
      Added value: +"Lowest modeled premium."
    • addedOutput schema / properties / monthly_estimates / properties / collision_claim / properties / upper / description
      Added value: +"Upper end of the typical range."
    • addedOutput schema / properties / monthly_estimates / properties / without / description
      Added value: +"Without collision or comprehensive coverage. Whole US dollars per month."
    • addedOutput schema / properties / monthly_estimates / properties / without / properties / lower / description
      Added value: +"Lower end of the typical range."
    • addedOutput schema / properties / monthly_estimates / properties / without / properties / max / description
      Added value: +"Highest modeled premium."
    • addedOutput schema / properties / monthly_estimates / properties / without / properties / median / description
      Added value: +"Median modeled premium."
    • addedOutput schema / properties / monthly_estimates / properties / without / properties / min / description
      Added value: +"Lowest modeled premium."
    • addedOutput schema / properties / monthly_estimates / properties / without / properties / upper / description
      Added value: +"Upper end of the typical range."
    • addedOutput schema / properties / projection_years / description
      Added value: +"Number of years the cumulative projections cover."
  2. Changed12 schema fields changed
    • 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": {
      +    "cumulative_annual_scenarios": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "cumulative_annual_premiums": {
      +            "items": {
      +              "type": "integer"
      +            },
      +            "type": "array"
      +          },
      +          "label": {
      +            "type": "string"
      +          },
      +          "scenario": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "scenario",
      +          "label",
      +          "cumulative_annual_premiums"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "disclaimer": {
      +      "type": "string"
      +    },
      +    "estimate_unit": {
      +      "type": "string"
      +    },
      +    "inputs": {
      +      "additionalProperties": true,
      +      "type": "object"
      +    },
      +    "monthly_estimates": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "both": {
      +          "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"
      +        },
      +        "both_claim": {
      +          "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"
      +        },
      +        "collision": {
      +          "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"
      +        },
      +        "collision_claim": {
      +          "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"
      +        },
      +        "without": {
      +          "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"
      +        }
      +      },
      +      "required": [
      +        "without",
      +        "collision",
      +        "both",
      +        "collision_claim",
      +        "both_claim"
      +      ],
      +      "type": "object"
      +    },
      +    "projection_years": {
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "inputs",
      +    "monthly_estimates",
      +    "projection_years",
      +    "cumulative_annual_scenarios",
      +    "estimate_unit",
      +    "disclaimer"
      +  ],
      +  "type": "object"
      +}
  3. First observed

TDQS

A3.9/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 real value beyond that by enumerating the returned scenarios (no coverage, collision only, both, after-claim variants) and warning that these are model estimates, not bindable quotes.

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?

Three sentences, front-loaded with purpose then outputs then the estimate caveat. Dense but nearly every clause earns its place; the long enumeration of return scenarios is the only slightly heavy part.

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?

Given an output schema exists, return values need not be explained, yet the description usefully summarizes them and flags the non-bindable nature of the estimates. Coverage is solid for a read-only calculator; only sibling differentiation is thin.

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 the schema already documents all 11 inputs, establishing a baseline of 3. The description references projection_years, a field not present in the input schema, but adds no syntax or default detail for the documented parameters.

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 (estimate collision/comprehensive cost) and scopes it to one driver and vehicle profile, which is precise. It does not differentiate itself from the sibling auto_estimates tool, leaving some ambiguity about which estimator to pick.

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 decision context clearly ('to help decide whether to carry them'), which tells the agent when this tool is appropriate. It offers no explicit exclusions or named alternatives, so it stops short of full routing 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