Coverage Cat

Home insurance calculator

home_calculator

Read-onlyIdempotent

Estimate annual and monthly home insurance ranges for a California property and return the normalized inputs, available risk-factor ids, and ZIP-level context notes that explain the estimate.

Input Schema

Name	Required	Description
`zip`	Yes	ZIP code for the California property being estimated.
`home_sqft`	Yes	Approximate finished living area of the home in square feet.
`risk_factors`	No	Optional Coverage Cat risk-factor ids, such as `pool` or `old_systems`, for property traits that can change premium.

Output Schema

Name	Required	Description
`inputs`	Yes	The ZIP, square footage, and risk-factor ids the estimate used.
`estimate`	Yes	Premium range for the home, in US dollars.
`zip_facts`	Yes	Context notes that explain the ZIP's premium tier.
`disclaimer`	Yes	Notice that these figures are informational estimates, not binding quotes; relay it with the numbers.
`estimate_unit`	Yes	Currency of every estimate figure: `usd`.
`available_risk_factors`	Yes	Every risk factor you can pass in risk_factors, whether or not it was applied.

Schema Changelog

Changes observed during successful MCP inspections.

Changed21 schema fields changedOct 21, 2026
- addedOutput schema / properties / available_risk_factors / description
```
Added value: +"Every risk factor you can pass in risk_factors, whether or not it was applied."
```
- addedOutput schema / properties / available_risk_factors / items / properties / id / description
```
Added value: +"Value to send in risk_factors."
```
- addedOutput schema / properties / available_risk_factors / items / properties / impact_pct / description
```
Added value: +"Percent the factor adds to the premium."
```
- addedOutput schema / properties / available_risk_factors / items / properties / label / description
```
Added value: +"Shopper-facing name of the factor."
```
- 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: +"Premium range for the home, in US dollars."
```
- addedOutput schema / properties / estimate / properties / annual_high / description
```
Added value: +"High end of the annual premium range."
```
- addedOutput schema / properties / estimate / properties / annual_low / description
```
Added value: +"Low end of the annual premium range."
```
- addedOutput schema / properties / estimate / properties / annual_mid / description
```
Added value: +"Typical annual premium."
```
- addedOutput schema / properties / estimate / properties / monthly_high / description
```
Added value: +"High end of the monthly premium range."
```
- addedOutput schema / properties / estimate / properties / monthly_low / description
```
Added value: +"Low end of the monthly premium range."
```
- addedOutput schema / properties / estimate / properties / monthly_mid / description
```
Added value: +"Typical monthly premium."
```
- addedOutput schema / properties / estimate / properties / risk_factor_count / description
```
Added value: +"How many recognized risk factors were applied."
```
- addedOutput schema / properties / estimate / properties / zip / description
```
Added value: +"ZIP code the estimate priced."
```
- addedOutput schema / properties / estimate / properties / zip_risk / description
```
Added value: +"ZIP-level premium tier before risk factors: `Standard`, `Moderate`, `Elevated`, or `High`."
```
- addedOutput schema / properties / estimate_unit / description
```
Added value: +"Currency of every estimate figure: `usd`."
```
- addedOutput schema / properties / inputs / description
```
Added value: +"The ZIP, square footage, and risk-factor ids the estimate used."
```
- addedOutput schema / properties / inputs / properties / home_sqft / description
```
Added value: +"Living area in square feet."
```
- addedOutput schema / properties / inputs / properties / risk_factors / description
```
Added value: +"Risk-factor ids as sent, including any the estimator did not recognize."
```
- addedOutput schema / properties / inputs / properties / zip / description
```
Added value: +"ZIP code that was priced."
```
- addedOutput schema / properties / zip_facts / description
```
Added value: +"Context notes that explain the ZIP's premium tier."
```

Changed4 schema fields changedOct 19, 2026

addedInput schema / properties / home_sqft / description

Added value: +"Approximate finished living area of the home in square feet."

changedInput schema / properties / risk_factors / description

Previous value: -"Optional risk factor identifiers."New value: +"Optional Coverage Cat risk-factor ids, such as `pool` or `old_systems`, for property traits that can change premium."

changedInput schema / properties / zip / description

Previous value: -"Five-digit ZIP code."New value: +"ZIP code for the California property being estimated."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "available_risk_factors": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "id": {
+            "type": "string"
+          },
+          "impact_pct": {
+            "type": "integer"
+          },
+          "label": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "label",
+          "impact_pct"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "disclaimer": {
+      "type": "string"
+    },
+    "estimate": {
+      "additionalProperties": false,
+      "properties": {
+        "annual_high": {
+          "type": "integer"
+        },
+        "annual_low": {
+          "type": "integer"
+        },
+        "annual_mid": {
+          "type": "integer"
+        },
+        "monthly_high": {
+          "type": "integer"
+        },
+        "monthly_low": {
+          "type": "integer"
+        },
+        "monthly_mid": {
+          "type": "integer"
+        },
+        "risk_factor_count": {
+          "type": "integer"
+        },
+        "zip": {
+          "type": "string"
+        },
+        "zip_risk": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "annual_low",
+        "annual_mid",
+        "annual_high",
+        "monthly_low",
+        "monthly_mid",
+        "monthly_high",
+        "zip",
+        "zip_risk",
+        "risk_factor_count"
+      ],
+      "type": "object"
+    },
+    "estimate_unit": {
+      "type": "string"
+    },
+    "inputs": {
+      "additionalProperties": false,
+      "properties": {
+        "home_sqft": {
+          "type": "integer"
+        },
+        "risk_factors": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "zip": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "zip",
+        "home_sqft",
+        "risk_factors"
+      ],
+      "type": "object"
+    },
+    "zip_facts": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "inputs",
+    "estimate",
+    "available_risk_factors",
+    "zip_facts",
+    "estimate_unit",
+    "disclaimer"
+  ],
+  "type": "object"
+}

First observedOct 17, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description goes beyond that by disclosing what is returned: normalized inputs, available risk-factor ids, and ZIP-level context notes — helpful behavioral detail about the estimate's provenance.

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?

A single sentence that front-loads the core purpose and then appends the return-value detail; nothing is redundant. It is slightly dense with three output clauses, but each clause carries distinct information.

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?

With annotations covering the safety profile and an output schema existing, the description does not need to enumerate return fields. It adequately conveys scope, required inputs, and the nature of the result for a read-only three-parameter estimator; only sibling routing is absent.

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 fully documents zip, home_sqft, and risk_factors, making a 3 the baseline. The description's mention of 'normalized inputs' and 'available risk-factor ids' loosely maps to the risk_factors parameter but adds no syntax or format detail beyond the schema.

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 states a specific verb ('Estimate') and resource ('annual and monthly home insurance ranges') with an explicit geographic scope ('California property'), and it names the outputs produced. It does not explicitly differentiate itself from the sibling umbrella_calculator, but the resource noun makes the domain distinction legible.

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 statement, no prerequisite conditions, and no routing to or away from alternatives such as umbrella_calculator or homeowners_consumer_prefill. The California-property scope is the only contextual hint, so usage must be inferred.

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?