Quotor

start_quote

Begin a new home, auto, or bundled insurance quote. Returns a quote ID to use on every following call. Call this when the customer wants to get an insurance price.

INTAKE ORDER (Kyle 2026-06-11 — collect in this order, ONE coherent chunk per turn):

HOME/BUNDLE: full name + date of birth for EVERYONE on the policy (relationship for non-PNI).
Address of the home + "is this a new purchase, or one you've owned a while?" (new purchase → ALSO capture current_address — where they live today; property.address stays the home being bought). Then mortgage + escrow + "roughly how old is the roof? — 'I don't know' is a fine answer" ride along (roof unknown → move on, never probe; roof REPLACED → one follow-up: hail-resistant / Class 1–4? → property.hail_resistant_roof + property.ul_impact_type). The home address doubles as auto garaging unless the cars live elsewhere.
AUTO/BUNDLE: year/make/model of every vehicle.
Any drivers NOT already named in step 1 — names + DOBs + relationship.
Email + phone, framed as "where should I send your final numbers?" — the consent line is REQUIRED on this turn.
ONE open question before firing: "Any coverages you want to tell me about before I run it?" Capture whatever they volunteer via update_quote and move on — do NOT turn this into a coverage consultation. Scheduled valuables (jewelry, art, guns, collections) are a POST-BIND follow-up: record them under the follow_ups patch branch and tell the customer "our team will add that right after we get this policy locked" — never try to add them mid-quote.

Then call get_quote_options immediately. Don't over-collect — the customer should reach prices fast.

Input Schema

TableJSON Schema

Name	Required	Description
`product`	Yes	Line of business to quote: 'auto', 'home', or 'bundle'.
`meta_codes`	No	Optional internal meta codes; ignored unless recognized.
`referral_source`	No	Optional referral/partner source tag for attribution.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`quote_id`	No
`session_expires_at`	No
`next_required_inputs`	No

TDQS

A4.4/5.0

Behavior5/5

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

Beyond annotations (readOnlyHint: false, openWorldHint: true), the description details behavioral traits: returns a quote ID, outlines a precise data collection sequence with prohibitions (e.g., roof unknown → move on, never probe; scheduled valuables are post-bind), and outlines the follow-up action (call get_quote_options). No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very verbose, including a detailed intake order with specific names, dates, and procedural instructions that extend far beyond a typical tool description. While the first sentence is clear, the overall length hinders quick scanning for an AI agent.

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 (3 parameters, output schema, annotations), the description is complete: it covers purpose, input requirements, step-by-step usage, behavioral constraints, and even the next call to get_quote_options. It provides all necessary context for correct invocation.

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 the schema already documents all three parameters. The description adds no extra semantic meaning to the parameters beyond repeating the product enum. For a high-coverage schema, 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 starts with a clear statement: 'Begin a new home, auto, or bundled insurance quote. Returns a quote ID to use on every following call.' This distinctly identifies the tool's function and differentiates it from sibling tools like resume_quote or get_quote_options which handle existing quotes.

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 says 'Call this when the customer wants to get an insurance price.' It provides a detailed step-by-step intake order, including when to stop collecting data and when to call get_quote_options. It also instructs not to over-collect, giving clear usage boundaries.

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?