Coverage Cat

Send shopper email verification

consumer_intake_verify_email

DestructiveIdempotent

When consumer_intake_issues reports verification.required, ask the shopper whether to send a verification email, then call with confirm_send: true. The link goes only to the application's email on file. Ask the shopper to open it, then poll consumer_intake_issues until verification.required is false. Never ask the shopper to paste the login link or code into chat.

Input Schema

Name	Required	Description
`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.
`confirm_send`	Yes	Confirm that the shopper asked to send a verification link to their application's email on file.
`idempotency_key`	No	Key you generate to identify one logical consumer_intake_verify_email request, so a retry cannot apply it twice. After a timeout or transport failure, retry with the same key and identical arguments to get the original result back; Coverage Cat keeps that result for 24 hours and rejects different arguments sent under a used key.
`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"
+}

AddedOct 31, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare mutation, irreversibility, and idempotency, so the description focuses on what annotations can't convey: the link only goes to the email on file and the shopper must never paste the link or code into chat. That is genuine security and eligibility context. It stops short of describing what the tool returns or failure modes (e.g. expired intake), which would push this to a 5.

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?

Four compact sentences in execution order: trigger, ask, call, poll, plus a guardrail. Front-loaded and free of restated metadata such as parameter types or return shape.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. The description supplies the remaining pieces an agent needs — trigger condition, consent step, follow-up polling, and privacy rule — which is everything required to call this correctly within a multi-step intake flow.

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% and the property descriptions already explain uid reuse, the confirm_send consent meaning, and idempotency-key retry semantics. The description reinforces the consent ordering behind confirm_send but adds no new syntax, format, or validation detail beyond the schema. Baseline 3 applies 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 — send a verification email to the shopper's email on file — and pins the trigger condition (`consumer_intake_issues` reports verification.required). It explicitly names the sibling it coordinates with, so the agent can separate this from consumer_intake_issues and consumer_intake_patch without opening schemas.

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?

Gives an explicit precondition (verification.required from consumer_intake_issues), an intermediate step (ask the shopper first), a hard invocation constraint (confirm_send: true), and a follow-up loop (poll consumer_intake_issues until the flag clears). When-to-use, when-not-to-call-yet, and what to do afterward are all covered.

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?