Quotor

check_quote_status

Read-only

Check rating + live-finishing progress. Call between wait-phase questions (every customer turn or two after get_quote_options). Returns one of:

'running' — indicatives still landing; continue the wait-phase conversation, call again next turn.
'quoted' — options[] is populated. CHECK THE 'finishing' BLOCK: when finishing.active=true, the exact bindable rates are STILL being captured live at the carrier portals — present the price ranges confidently as honest estimates (the low end is the carrier's own starting figure; NEVER promise the final number can't exceed the range), keep the conversation going, and keep checking on later turns; cards harden to 'verified' automatically as walks complete. When finishing.active=false, the run is over: cards marked 'verified' are exact bindable numbers; anything still 'estimate' stays a range that a licensed agent confirms at bind.
'timeout' — carriers took too long; offer to retry with get_quote_options.
'needs_data' — carriers can't rate until the customer supplies the fields in needs.prompts (e.g. a driver's license number, a VIN, or an additional driver's name/date of birth — each prompt says who/what it's for). Ask the customer conversationally, apply the answers with update_quote (the prompt 'field' values are the exact patch paths, e.g. drivers[1].date_of_birth), then call get_quote_options to re-run. Repeat as many times as it takes — this is an ask, NOT a failure. needs may also ride along with 'quoted' when one line rated and the other still needs info.
'error' — all carriers errored; flag it honestly and offer to retry. Each option carries rate_state ('verified' | 'verifying' | 'estimate') and, for unverified options, price_range {low, high}. NEVER mention carrier counts or real carrier names in chat.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`quote_id`	Yes	The quote session id to poll.
`max_options`	No	Maximum options to return per line (1-5, default 3).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`needs`	No
`status`	No
`options`	No
`quote_id`	No
`progress_pct`	No
`carrier_names_revealed`	No

TDQS

A4.6/5.0

Behavior5/5

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

Annotations provide readOnlyHint and openWorldHint, but the description adds critical behavioral context: detailed explanation of each status, the distinction between finishing.active=true/false for 'quoted', and the warning about never mentioning carrier counts or real carrier names.

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 description is well-structured with bullet points for each status, making it easy to scan. It front-loads the purpose. While it is moderately lengthy, every sentence adds value. Could be slightly more concise but remains clear.

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?

Given the tool's complexity (multiple statuses, interactions with other tools, and detailed return value interpretation), the description is highly complete. It explains what to do for each scenario and references the output schema implicitly, making it fully informative for an AI agent.

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% for both parameters (quote_id, max_options). The description does not add significant new meaning beyond the schema, which already includes descriptions. Baseline 3 is appropriate.

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?

The description clearly states 'Check rating + live-finishing progress.' It specifies the verb 'Check' and the resource 'quote status', distinguishing it from siblings like get_quote_options which initiates quotes and get_option_details which retrieves specific option details.

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?

The description explicitly states when to call: 'between wait-phase questions (every customer turn or two after get_quote_options)'. It also provides guidance for each return status, including when to use alternative tools like get_quote_options for 'timeout' and update_quote for 'needs_data'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Quotor tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation4/5

Each tool targets a distinct step in the quoting workflow (eligibility, start, update, status, options, details, binding, resume, lead capture). Some overlap exists between get_bind_link and request_bind_inline, but descriptions clarify usage. Overall clear.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern using snake_case (e.g., check_eligibility, get_quote_options, request_bind_inline). No mixing of conventions.

Tool Count5/5

11 tools cover the insurance quoting lifecycle well. The number is appropriate for the domain without being sparse or overwhelming.

Completeness4/5

The tool set covers the major steps: eligibility, quoting, status, options, updates, binding, and lead capture. Missing a quote cancellation or decline tool, but core workflows are complete.

Resources

Need Help?