Quotor

by ai.quotor.mcp

Overview Discussions Admin

Check quote status

check_quote_status

Idempotent

Reports rating progress and, once available, the quote options. status is one of:

running: prices are still arriving; check again in a turn or two.
quoted: options are ready. While finishing.active is true, Libertas is still capturing exact rates, so ranges are estimates (the final number may land within or below the range, but that isn't guaranteed); check back later. Options marked 'verified' are exact, bindable numbers.
needs_data: carriers need more information first. needs.prompts lists each item, who it's for, and the update_quote field to set; apply the customer's answers, then call get_quote_options again. When needs.secure_link is present, that item (a driver's license number) is entered on Libertas's secure page instead of in chat: share the link with the customer, and rates re-run automatically once they submit it.
timeout or error: offer to try again with get_quote_options. Carriers appear as 'Carrier A-Home', 'Carrier B-Auto', and so on; the real carrier name is shown on Libertas's secure bind page.

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
`data_warnings`	No
`carrier_names_revealed`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 4, 2026
- addedOutput schema / properties / data_warnings
```
Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
```

Changed2 schema fields changedJul 15, 2026

changedOutput schema / description

Previous value: -"Live rating status plus masked options (carriers hidden until the bind step)."New value: +"Live rating status plus masked options (carriers hidden until the bind step). Status 'needs_data' means the customer must supply the fields in `needs.prompts` (apply via update_quote, then re-run get_quote_options)."

addedOutput schema / properties / needs

Added value: +{
+  "type": [
+    "object",
+    "null"
+  ]
+}

First observedJun 26, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, idempotent=true): discloses that ranges are estimates until finishing.active clears, that 'verified' options are exact/bindable, the secure-link flow for driver's license data, and that carrier names ('Carrier A-Home') are anonymized stand-ins. This is rich behavioral context an agent could not infer from structured fields.

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?

Front-loaded with the core purpose followed by a clean enum-style breakdown of statuses. It is long, but the length is justified by four distinct status branches; minor redundancy in phrasing keeps it just short of 5.

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-format detail is rightly omitted, and the description still covers every status outcome plus the follow-up action for each. Nothing an agent needs to poll and act correctly is missing.

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 quote_id and max_options are already documented in the schema; the description adds nothing about either parameter. Baseline 3 applies since 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+resource ('Reports rating progress and... the quote options') and is clearly distinguishable from siblings like get_quote_options and update_quote, which it explicitly routes to. An agent knows exactly what this returns.

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

Usage Guidelines4/5

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

Provides explicit branch-by-branch guidance: poll again for 'running', wait for 'quoted', apply answers then re-call get_quote_options for 'needs_data', retry for timeout/error. It routes to alternatives well, though it never states when NOT to use this tool or how it differs from resume_quote/start_quote.

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

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?