Coverage Cat

Get homeowners policy

homeowners_consumer_policy

Read the current bound or cancelled homeowners policy record, policy documents, and any existing cancellation, refund, or support request history. Reuse uid and the latest intake_access_token from the previous successful Coverage Cat response on each follow-up. MCP 2026-07-28 is stateless and requires that token. Legacy MCP hosts may also preserve hidden shopper session authorization. Keep tokens private and stay on this same MCP follow-up tool. This request records access attribution and rotates follow-up access, but does not advance or change policy state. Use it after Coverage Cat reports a policy on file, or after a service request is opened, to show policy facts without switching to delegated tools.

Input Schema

Name	Required	Description	Default
`uid`	Yes	Coverage Cat intake uid for the existing authorized intake or returned by `umbrella_consumer_prefill` and echoed on every follow-up response. Reuse it for each follow-up call on the same application.
`intake_access_token`	No	Send the latest intake_access_token from the previous successful Coverage Cat response on each follow-up. Required for stateless MCP 2026-07-28 requests; also accepted by legacy hosts. Keep it private and never show it to the shopper.

Output Schema

Name	Required	Description
`uid`	Yes	Coverage Cat intake uid for the current handoff.
`line`	No
`offers`	No
`policy`	No
`review`	No	Structured review card or selected-offer review block.
`schema`	No	Supplemental schema hints for homeowners review payloads.
`status`	Yes
`sandbox`	No	True when Coverage Cat is returning consumer sandbox test data rather than a live shopper workflow.
`support`	No
`uploaded`	No
`documents`	No
`expires_at`	No	When the current consumer handoff expires.
`offers_url`	No	Coverage Cat browser URL for the selected offer or offer-tracking page.
`payment_ui`	No
`next_action`	No	A structured hint for the next allowed tool or endpoint action.
`payment_url`	No	Coverage Cat browser URL for secure payment fallback.
`post_choose`	No	Structured post-choose state after a quoted umbrella offer is selected.
`conversation`	No
`review_items`	No
`review_token`	No	Opaque review token for delegated review-style submit paths.
`verification`	No
`detail_status`	No
`known_summary`	No	Structured facts Coverage Cat can safely summarize at this stage.
`next_question`	No	The current shopper-owned question bundle or bind-stage question.
`offer_summary`	No
`payment_setup`	No
`preview_token`	No	Opaque bind-preview token for the next homeowners bind confirmation.
`missing_fields`	No	Structured missing-value hints for homeowners pre-submit review.
`payment_status`	No
`pending_fields`	No	Structured missing-value hints for umbrella pre-submit review.
`selected_offer`	No
`uploaded_count`	No
`field_estimates`	No
`service_preview`	No
`service_request`	No
`purchase_preview`	No
`response_summary`	No
`review_estimates`	No
`service_requests`	No
`agent_instructions`	No
`poll_after_seconds`	No
`selection_guidance`	No	Guidance for completing an offer choice in one shopper-facing reply.
`compare_details_url`	No	Coverage Cat browser URL for compare-details follow-up.
`intake_access_token`	No	Short-lived follow-up bearer. On REST, send it back as Authorization for the next `/api/intake/{uid}` call. On MCP, retry the same follow-up tool with this token only when your host cannot preserve Coverage Cat's hidden shopper session. Never display it to the shopper.
`notification_channel`	No
`user_action_required`	No
`application_submitted`	No
`required_upload_types`	No
`credit_consent_question`	No
`credit_consent_disclosure`	No	Versioned canonical text that must be shown verbatim; echo version and text_hash with the user's response.
`payment_collection_supported`	No
`monoline_mvr_consent_question`	No
`contact_preferences_disclosures`	No	Optional versioned service-contact disclosures for the phone number on file; no marketing consent and no purchase requirement.
`monoline_mvr_consent_disclosure`	No	Versioned Monoline-specific text that must be shown verbatim with its source URL; echo version and text_hash with the user's response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedNov 5, 2026

addedOutput schema / properties / contact_preferences_disclosures / properties / service_call / properties / source_updated_at
```
Added value: +{
+  "format": "date",
+  "type": "string"
+}
```
addedOutput schema / properties / contact_preferences_disclosures / properties / service_call / properties / source_url
```
Added value: +{
+  "format": "uri",
+  "type": "string"
+}
```
addedOutput schema / properties / contact_preferences_disclosures / properties / service_sms / properties / source_updated_at
```
Added value: +{
+  "format": "date",
+  "type": "string"
+}
```
addedOutput schema / properties / contact_preferences_disclosures / properties / service_sms / properties / source_url
```
Added value: +{
+  "format": "uri",
+  "type": "string"
+}
```
addedOutput schema / properties / credit_consent_disclosure / properties / source_updated_at
```
Added value: +{
+  "format": "date",
+  "type": "string"
+}
```
addedOutput schema / properties / credit_consent_disclosure / properties / source_url
```
Added value: +{
+  "format": "uri",
+  "type": "string"
+}
```

changedOutput schema / properties / detail_status / enum

Previous value: -[
-  "abandoned",
-  "blocked",
-  "bound",
-  "cancelled",
-  "chosen",
-  "credit_consent_pending",
-  "credit_consent_required",
-  "dev_success",
-  "documents_needed",
-  "documents_pending_review",
-  "email_sent",
-  "in_review",
-  "ineligible",
-  "info_requested",
-  "needs_more_info",
-  "needs_more_info_to_bind",
-  "no_policy",
-  "no_chosen_offer",
-  "no_quotes",
-  "no_selection",
-  "ok",
-  "payment_collection_ready",
-  "payment_needed",
-  "pending",
-  "pending_quotes",
-  "queued",
-  "quote_rate_limited",
-  "quoted",
-  "ready_for_review",
-  "ready_for_submission",
-  "ready_to_finalize",
-  "review_pending",
-  "service_preview",
-  "service_requested",
-  "sandbox_unsupported",
-  "stale_selection",
-  "verifying_documents",
-  "waiting_on_carrier",
-  "waiting_on_documents",
-  "waiting_on_payment"
-]New value: +[
+  "abandoned",
+  "blocked",
+  "bound",
+  "cancelled",
+  "chosen",
+  "credit_consent_pending",
+  "credit_consent_required",
+  "monoline_mvr_consent_required",
+  "dev_success",
+  "documents_needed",
+  "documents_pending_review",
+  "email_sent",
+  "in_review",
+  "ineligible",
+  "info_requested",
+  "needs_more_info",
+  "needs_more_info_to_bind",
+  "no_policy",
+  "no_chosen_offer",
+  "no_quotes",
+  "no_selection",
+  "ok",
+  "payment_collection_ready",
+  "payment_needed",
+  "pending",
+  "pending_quotes",
+  "queued",
+  "quote_rate_limited",
+  "quoted",
+  "ready_for_review",
+  "ready_for_submission",
+  "ready_to_finalize",
+  "review_pending",
+  "service_preview",
+  "service_requested",
+  "sandbox_unsupported",
+  "stale_selection",
+  "verifying_documents",
+  "waiting_on_carrier",
+  "waiting_on_documents",
+  "waiting_on_payment"
+]

addedOutput schema / properties / monoline_mvr_consent_disclosure

Added value: +{
+  "additionalProperties": false,
+  "description": "Versioned Monoline-specific text that must be shown verbatim with its source URL; echo version and text_hash with the user's response.",
+  "properties": {
+    "kind": {
+      "const": "monoline_mvr",
+      "type": "string"
+    },
+    "source_updated_at": {
+      "format": "date",
+      "type": "string"
+    },
+    "source_url": {
+      "format": "uri",
+      "type": "string"
+    },
+    "text": {
+      "minLength": 1,
+      "type": "string"
+    },
+    "text_hash": {
+      "pattern": "^[a-f0-9]{64}$",
+      "type": "string"
+    },
+    "version": {
+      "minLength": 1,
+      "type": "string"
+    }
+  },
+  "required": [
+    "kind",
+    "version",
+    "text",
+    "text_hash",
+    "source_url",
+    "source_updated_at"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / monoline_mvr_consent_question
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / properties / status / enum

Previous value: -[
-  "abandoned",
-  "blocked",
-  "bound",
-  "cancelled",
-  "chosen",
-  "credit_consent_pending",
-  "credit_consent_required",
-  "dev_success",
-  "documents_needed",
-  "documents_pending_review",
-  "email_sent",
-  "in_review",
-  "ineligible",
-  "info_requested",
-  "needs_more_info",
-  "needs_more_info_to_bind",
-  "no_policy",
-  "no_chosen_offer",
-  "no_quotes",
-  "no_selection",
-  "ok",
-  "payment_collection_ready",
-  "payment_needed",
-  "pending",
-  "pending_quotes",
-  "queued",
-  "quote_rate_limited",
-  "quoted",
-  "ready_for_review",
-  "ready_for_submission",
-  "ready_to_finalize",
-  "review_pending",
-  "service_preview",
-  "service_requested",
-  "sandbox_unsupported",
-  "stale_selection",
-  "verifying_documents",
-  "waiting_on_carrier",
-  "waiting_on_documents",
-  "waiting_on_payment"
-]New value: +[
+  "abandoned",
+  "blocked",
+  "bound",
+  "cancelled",
+  "chosen",
+  "credit_consent_pending",
+  "credit_consent_required",
+  "monoline_mvr_consent_required",
+  "dev_success",
+  "documents_needed",
+  "documents_pending_review",
+  "email_sent",
+  "in_review",
+  "ineligible",
+  "info_requested",
+  "needs_more_info",
+  "needs_more_info_to_bind",
+  "no_policy",
+  "no_chosen_offer",
+  "no_quotes",
+  "no_selection",
+  "ok",
+  "payment_collection_ready",
+  "payment_needed",
+  "pending",
+  "pending_quotes",
+  "queued",
+  "quote_rate_limited",
+  "quoted",
+  "ready_for_review",
+  "ready_for_submission",
+  "ready_to_finalize",
+  "review_pending",
+  "service_preview",
+  "service_requested",
+  "sandbox_unsupported",
+  "stale_selection",
+  "verifying_documents",
+  "waiting_on_carrier",
+  "waiting_on_documents",
+  "waiting_on_payment"
+]

Changed1 schema field changedNov 4, 2026

changedInput schema / properties / uid / description

Previous value: -"Coverage Cat intake uid returned by `umbrella_consumer_prefill` or `homeowners_consumer_prefill` and echoed on every follow-up response. Reuse it for each follow-up call on the same application."New value: +"Coverage Cat intake uid for the existing authorized intake or returned by `umbrella_consumer_prefill` and echoed on every follow-up response. Reuse it for each follow-up call on the same application."

Changed2 schema fields changedNov 4, 2026

addedOutput schema / properties / contact_preferences_disclosures

Added value: +{
+  "additionalProperties": false,
+  "description": "Optional versioned service-contact disclosures for the phone number on file; no marketing consent and no purchase requirement.",
+  "properties": {
+    "service_call": {
+      "additionalProperties": false,
+      "description": "Optional service-call disclosure; show its text verbatim before recording a choice.",
+      "properties": {
+        "kind": {
+          "const": "service_call",
+          "type": "string"
+        },
+        "text": {
+          "minLength": 1,
+          "type": "string"
+        },
+        "text_hash": {
+          "pattern": "^[a-f0-9]{64}$",
+          "type": "string"
+        },
+        "version": {
+          "minLength": 1,
+          "type": "string"
+        }
+      },
+      "required": [
+        "kind",
+        "version",
+        "text",
+        "text_hash"
+      ],
+      "type": "object"
+    },
+    "service_sms": {
+      "additionalProperties": false,
+      "description": "Optional service-text disclosure; show its text verbatim before recording a choice.",
+      "properties": {
+        "kind": {
+          "const": "service_sms",
+          "type": "string"
+        },
+        "text": {
+          "minLength": 1,
+          "type": "string"
+        },
+        "text_hash": {
+          "pattern": "^[a-f0-9]{64}$",
+          "type": "string"
+        },
+        "version": {
+          "minLength": 1,
+          "type": "string"
+        }
+      },
+      "required": [
+        "kind",
+        "version",
+        "text",
+        "text_hash"
+      ],
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / credit_consent_disclosure

Added value: +{
+  "additionalProperties": false,
+  "description": "Versioned canonical text that must be shown verbatim; echo version and text_hash with the user's response.",
+  "properties": {
+    "kind": {
+      "const": "credit_report",
+      "type": "string"
+    },
+    "text": {
+      "minLength": 1,
+      "type": "string"
+    },
+    "text_hash": {
+      "pattern": "^[a-f0-9]{64}$",
+      "type": "string"
+    },
+    "version": {
+      "minLength": 1,
+      "type": "string"
+    }
+  },
+  "required": [
+    "kind",
+    "version",
+    "text",
+    "text_hash"
+  ],
+  "type": "object"
+}

Changed1 schema field changedOct 31, 2026

addedOutput schema / properties / verification

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "instructions": {
+      "type": "string"
+    },
+    "request_tool": {
+      "type": "string"
+    },
+    "required": {
+      "type": "boolean"
+    },
+    "retry_after_seconds": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "status": {
+      "enum": [
+        "required",
+        "pending",
+        "verified",
+        "not_required"
+      ],
+      "type": "string"
+    },
+    "status_tool": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "status",
+    "required",
+    "retry_after_seconds",
+    "request_tool",
+    "status_tool",
+    "instructions"
+  ],
+  "type": "object"
+}

Changed1 schema field changedOct 31, 2026

changedInput schema / properties / intake_access_token / description

Previous value: -"Bearer fallback for this same MCP follow-up tool when your host cannot preserve Coverage Cat's hidden shopper session. Send the intake_access_token from the previous successful Coverage Cat response and never show it to the shopper."New value: +"Send the latest intake_access_token from the previous successful Coverage Cat response on each follow-up. Required for stateless MCP 2026-07-28 requests; also accepted by legacy hosts. Keep it private and never show it to the shopper."

Changed2 schema fields changedOct 19, 2026

changedInput schema / properties / intake_access_token / description

Previous value: -"Optional bearer fallback for this same MCP follow-up tool when your host cannot preserve Coverage Cat's hidden shopper session. Reuse the latest token from the previous successful Coverage Cat response and never show it to the shopper."New value: +"Bearer fallback for this same MCP follow-up tool when your host cannot preserve Coverage Cat's hidden shopper session. Send the intake_access_token from the previous successful Coverage Cat response and never show it to the shopper."

addedInput schema / properties / uid / description

Added value: +"Coverage Cat intake uid returned by `umbrella_consumer_prefill` or `homeowners_consumer_prefill` and echoed on every follow-up response. Reuse it for each follow-up call on the same application."

First observedOct 17, 2026

TDQS

A4.1/5.0

Behavior4/5

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

The description earns credit for explaining the otherwise puzzling readOnlyHint=false: the call "records access attribution and rotates follow-up access, but does not advance or change policy state." It also discloses statelessness under MCP 2026-07-28, token privacy requirements, and legacy host session behavior. It stops short of saying how token rotation affects a stale/expired token or what happens when no policy is on file.

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?

The first sentence front-loads what the tool returns, and the operational constraints follow in a logical order. Some redundancy exists between "stay on this same MCP follow-up tool" and "without switching to delegated tools," and the legacy-host sentence is marginally tangential, but nearly every sentence carries actionable 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 an output schema present, return-value detail is correctly omitted, and the description covers auth, statelessness, side effects, and placement in the workflow. What remains missing is error/edge behavior — e.g., what happens if no policy is on file yet or if the token is no longer the latest one.

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 both parameters are already documented in the input schema, which sets the baseline at 3. The description does add a usage rule beyond the schema — reuse the latest token from the previous successful response on every follow-up — but it largely restates the schema wording about uid and token privacy rather than adding new format or failure semantics.

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 opening sentence gives a precise verb ("Read") and enumerates the exact resources returned: the bound or cancelled homeowners policy record, policy documents, and cancellation/refund/support request history. It is clearly distinct from umbrella-oriented siblings by naming homeowners policy scope, but it never names the parallel umbrella_consumer_policy or homeowners_consumer_service tools, so the differentiation is implied rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states explicit triggers — "after Coverage Cat reports a policy on file, or after a service request is opened" — and an explicit boundary: show policy facts "without switching to delegated tools" and "stay on this same MCP follow-up tool." That is a when-to-use plus a when-not-to-use routing instruction, which is the full bar.

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?