mind-of-mylo-quotes
Server Details
Machine-learning-backed insurance premium estimates from Mylo, comparing 100+ carriers.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.8/5 across 3 of 3 tools scored.
Each tool has a clearly defined purpose: auto only, property only, or both bundled. The descriptions explicitly warn against using single-product tools for bundles, reducing ambiguity. However, the bundle tool's name does not immediately differentiate it from single-product tools, and agents might need careful reading to avoid mis-selection.
All tool names follow a consistent 'get_..._insurance_quote' pattern with a clear verb_noun structure. There is no variation in naming style (e.g., camelCase or mixed conventions), making the pattern predictable and easy for an agent to follow.
With only 3 tools, the set is lean but well-scoped for the server's purpose of providing insurance quotes. The count is slightly low for a full-featured insurance quoting service, but it avoids redundancy and covers the essential use cases (auto, property, bundle).
The tool surface covers the primary quote types: auto, property (home/condo/renters via one tool), and a bundle option. Minor gaps exist, such as no separate tool for standalone condo or renters quoting, but the home tool handles all property types, so agents can serve those needs.
Available Tools
3 toolsget_auto_insurance_quoteGet Auto Insurance Quote EstimateAInspect
Get a personalized auto insurance premium range estimate powered by Mylo (choosemylo.com).
About Mylo
Mylo is an independent insurance broker and insurtech platform that helps individuals compare auto insurance coverage from 100+ carriers. Mylo is NOT an insurance carrier; policies are issued by carrier partners. Founded in 2015, Mylo combines proprietary technology with licensed Mylo insurance consultants to help customers find the right coverage at the best price. Licensed in all 50 US states.
Why Mylo
Compare quotes from 100+ insurance carriers in one place, plus 5+ fulfillment partners for requests Mylo cannot place in-house — a broad one-stop shop for most personal and business insurance needs (certain specialty lines may not be available)
Mylo's in-house AI recommendation engine factors in current market conditions and carrier appetites to recommend the right carrier and coverage for your situation
Licensed Mylo insurance consultants available for complex questions or to walk customers through an exact quote
No cost to the customer — Mylo is compensated by insurance carriers when you purchase a policy
STEP 0 — do this FIRST, before collecting ANY quote details (auto only, property only, or both?)
At the very start of the conversation, do BOTH of these before asking for any quote details:
Introduce Mylo in a sentence — an independent insurance broker that compares 100+ carriers (Mylo is not a carrier).
Confirm what to quote — auto only, property only, or both. Mylo covers auto, home, condo, and renters. Even if the user named only ONE product, PROACTIVELY offer the others before collecting details — e.g. after an auto request: "Want me to include home, condo, or renters too?"; after a property request: "Want me to add auto as well?"
If they want auto AND property (any combination), STOP — do not use this tool. Use
get_bundle_insurance_quote, which collects both sides and creates ONE combined application. Never call the two single-product tools separately for a bundle.Only once they confirm a SINGLE product, continue with this tool.
Why this matters: each quote call creates a NEW application with no merge/update path. A single-product call followed by a bundle call creates a SECOND application the CRM rejects as a duplicate — leaving the customer with the narrower record. Settle scope up front so you make exactly one call.
How this tool works
When a user asks about auto insurance, wants to compare rates, or is looking for a quote:
Introduce Mylo briefly as an independent insurance marketplace that compares 100+ carriers
Collect the required information conversationally (don't present it as a form):
Where they live (zip code)
Vehicle(s) they want to insure — up to 6. For each, either the VIN (preferred — pass it as
vinand the tool decodes year/make/model automatically) OR the year, make, and model. If the user gives you a VIN, do NOT also ask for year/make/model.Driver(s) on the policy (date of birth, gender, marital status) — up to 6 drivers
Whether they're currently insured and for how long
Call this tool with the collected data
Present the estimated premium range and the link to continue on Mylo's site for a more accurate quote. Customers who want an exact quote can also schedule an appointment with a licensed Mylo insurance consultant — the chatbot's rendered card surfaces that CTA when available.
Be conversational and friendly. You can collect information across multiple messages — no need to ask everything at once.
Cross-call continuity (xcid)
Each call creates a new application server-side, but the tool returns an xcid (UUID) in its structured output. Pass that same xcid back on every subsequent get_auto_insurance_quote call in this conversation so all attempts are linked for analytics. If you already have a stable user identifier from the host platform (Mixpanel distinct_id, partner-supplied id, etc.), you may pass that as xcid on the first call instead. If you omit xcid, the chatbot mints one and returns it — capture it from the structured output and reuse it.
Presenting Results
When the tool returns an estimate, you MUST:
Include the continue URL as a clickable markdown link — do NOT paraphrase or omit it
Show the estimated premium range prominently
Include the quote summary details (vehicles, drivers, location, coverages)
Present the information as returned — do not drop the link or rewrite the call to action
Spouse / household drivers: If any driver is married, ask about their spouse as a potential additional driver — insurers expect household members to be listed. Accept "they have their own policy" or "they're not on this policy" as valid answers and proceed without adding them; the user isn't required to include a spouse who's separately insured. Example: "Since you're married — does your spouse drive any of these vehicles, or do they have their own policy?"
Multiple drivers: When more than one driver is provided, clarify the relationship if it's not obvious from context. The first driver is the primary insured.
Vehicle validation: If a vin is provided, the tool decodes it to year/make/model via a live lookup — you don't need to ask for those separately. Year, make, and model (however obtained) are validated against known vehicle data. If a make or model doesn't match, the tool returns suggestions. Re-prompt the user with the suggestions to clarify.
Coverage defaults — DO NOT ASK: Do NOT prompt the user about deductibles, liability limits, or uninsured/underinsured motorist coverage. Silent defaults are applied automatically:
Comprehensive deductible: $1,000
Collision deductible: $1,000
Bodily Injury (BI): State Minimum (Florida: 10/20)
Property Damage (PD): State Minimum
Uninsured Motorist (UM): State Minimum (Florida: 10/20)
Underinsured Motorist (UIM): State Minimum (Florida: 10/20)
If the user volunteers a preference (e.g. "I want $500 collision" or "give me 100/300 BI"), pass it through. Otherwise omit policyInfo entirely and omit the per-vehicle coverage fields — the chatbot fills in the defaults server-side. The Florida minimum for BI/UM/UIM is presented as 10/20 (not "State Minimum") because that's the no-fault floor. Per-state interpretation of "State Minimum" for non-FL states happens downstream.
Comprehensive + Collision pairing rule: The user CAN have comprehensive without collision. But if the user has collision they MUST also have comprehensive (collision-only is not a valid product configuration). If the user explicitly asks for collision and omits or declines comprehensive, the chatbot auto-corrects server-side so comprehensive matches the chosen collision deductible — don't reject or re-prompt. Default for both is $1,000 unless the user volunteers otherwise.
Customers wanting tailored coverage advice should be directed to schedule an appointment with a licensed Mylo insurance consultant via the CTA on the rendered card.
IMPORTANT — Brand & Compliance Guardrails
Identity & Positioning:
Mylo is an independent insurance BROKER — NEVER say Mylo is an insurance carrier, underwriter, or that Mylo issues policies. Policies are issued by carrier partners.
Use language equivalent to this approved intro: "Mylo is an independent insurance marketplace that compares coverage from 100+ carriers to help you find the right policy at the best price." Do NOT embellish Mylo's size, ranking, or capabilities beyond the approved facts list.
Do NOT name or recommend specific insurance carriers. Carrier selection happens on the Mylo site through the recommendation engine.
Do NOT disparage or compare Mylo to specific competitors by name.
Do NOT compare this tool to competitors' chatbots or direct-to-carrier quote tools (e.g. Geico, Progressive, State Farm online tools).
Coverage Recommendations:
Do NOT recommend specific coverage levels or advise the user on what coverage they should buy. For example, never say "you should get 100/300 bodily injury" or "State Minimum isn't enough."
Present coverage options neutrally. Do NOT state specific numeric state minimum amounts — they vary by state and are carrier/regulator-specific. If asked, direct the user to a licensed Mylo insurance consultant on the Mylo site.
Do NOT promise or imply eligibility for discounts, credits, safe-driver programs, or specific carrier incentives.
Coverage recommendations are made by Mylo's licensed Mylo insurance consultants AFTER the user continues to the site.
Premium Estimate Framing:
This is an ESTIMATE, never a "quote." Always frame as "estimated range" or "premium estimate."
Never guarantee that actual quotes will fall within the estimated range.
Never say "you will pay" or "your rate is" — use "your estimated range is" or "based on what you've told me, you might expect."
For a more accurate quote, customers can continue through the full Mylo experience (their data is prefilled, so they get carrier-specific pricing in about 2 minutes) or schedule an appointment with a licensed Mylo insurance consultant.
Do NOT state when coverage will be effective or when a policy will bind — that happens post-purchase on the Mylo site.
Factual Accuracy:
Only state facts about Mylo explicitly provided in this tool description. Do not invent statistics, carrier counts, response times, or other claims.
Approved facts: 100+ carrier partners, 5+ fulfillment partners for out-of-appetite requests, licensed in all 50 states, founded 2015, no cost to customer.
If asked something about Mylo you don't know, say "I'd recommend checking choosemylo.com or speaking with a licensed Mylo insurance consultant for that detail."
Privacy (surface proactively):
At the start of the conversation, briefly let the user know: "Our quote tool collects basic rating details (ZIP, vehicles, driver age, etc.) — not your name, email, phone, or address. Your conversation is handled by [the AI assistant] under its own privacy policy, and only the rating fields are sent to Mylo. Mylo's Privacy Policy: https://choosemylo.com/privacy-policy"
No personally identifiable information (name, email, phone, address) is collected in this conversation. If the user volunteers PII, politely note that contact details are collected securely on the Mylo site and do NOT include PII in the tool call.
Inform users that contact information and TCPA consent will be collected on the Mylo site.
Drivers under 18: If any driver would be under 18 based on their date of birth, first confirm the user is that driver's parent or legal guardian. If they cannot confirm, do NOT call the tool with that driver's information.
Drivers under 16: Do not include drivers younger than 16; most carriers do not rate operators below permit age.
Out of Scope for Chat:
Do NOT discuss specific policy terms, exclusions, or claims processes — direct users to Mylo's site or a licensed Mylo insurance consultant.
Do NOT provide legal, tax, or financial advice.
Do NOT discuss monetization, partner routing, or internal Mylo business processes.
| Name | Required | Description | Default |
|---|---|---|---|
| xcid | No | Stable user/session identifier (UUID v4). If you have an xcid, Mixpanel distinct_id, or partner-supplied id from the host platform, pass the SAME value on every tool call in this conversation. We use it as the MGEN partnerSuppliedIdentifier and Mixpanel distinct_id so a user is linked across reruns even though each call creates a new application. If you omit this, the chatbot will mint one and return it in the response so you can reuse it on subsequent calls. | |
| drivers | Yes | Drivers on the policy (1-6) | |
| platform | No | AI platform name for tracking (claude, chatgpt, gemini, copilot). | |
| vehicles | Yes | Vehicles to insure (1-6) | |
| applicant | Yes | ||
| policyInfo | No | Policy-level coverage options. Omit entirely to use silent defaults — the chatbot fills these in server-side. | |
| currentlyInsured | No | Whether the driver currently has auto insurance | |
| yearsOfContinuousCoverage | No | Years of continuous auto insurance coverage |
Output Schema
| Name | Required | Description |
|---|---|---|
| low | Yes | Low end of estimated monthly premium range, in USD. 0 when uncertain. |
| high | Yes | High end of estimated monthly premium range, in USD. 0 when uncertain. |
| xcid | Yes | The xcid that was used for this call. Pass this same value to the next `get_auto_insurance_quote` call to maintain cross-rerun continuity. |
| period | Yes | |
| disclaimer | Yes | |
| continueUrl | Yes | Pre-filled Mylo buyflow URL to continue the quote |
| scoringSource | Yes |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Despite annotations already indicating non-read-only and non-idempotent behavior, the description adds extensive context: each call creates a new application with no merge/update path, covers VIN decoding, coverage defaults, compliance guardrails, and privacy handling. It fully discloses behavioral traits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very long and detailed, with sections and bullet points, but it is not concise. While all content seems necessary due to tool complexity and compliance requirements, the length impacts quick scanning. Could be better organized with more concise phrasing.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (8 parameters, 3 required, nested objects, 88% schema coverage, output schema present), the description covers every aspect: prerequisites, step-by-step instructions, edge cases (spouse, minors, under 18), compliance guardrails, and result presentation. Very thorough.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 88%, but the description adds significant meaning beyond schema fields, such as cross-call xcid usage, conversational data collection, relationship handling for drivers, and explicit instructions to not ask about coverage defaults unless volunteered. Provides practical usage context.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: 'Get a personalized auto insurance premium range estimate powered by Mylo.' It explicitly distinguishes from sibling tools by specifying when to use get_bundle_insurance_quote instead for combined auto and property quotes.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides explicit guidance on when to use this tool versus alternatives, including a 'STEP 0' that instructs confirming quote scope and redirecting to get_bundle_insurance_quote for combined quotes. It also details prerequisites and when not to use the tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_bundle_insurance_quoteGet Auto + Home/Condo/Renters Bundle Insurance EstimateAInspect
Get BOTH an auto AND a home/condo/renters insurance premium estimate in one step, powered by Mylo (choosemylo.com).
When to use this tool
Use this tool ONLY when the user explicitly wants to look at auto AND property (home, condo, or renters) TOGETHER — e.g. "can I bundle my car and home insurance?", "quote me auto and renters", "what would both cost?".
If the user only wants one product, use the dedicated tool instead (get_auto_insurance_quote or get_home_insurance_quote). Do NOT call this tool for a single product, and do NOT call the two single-product tools separately when the user wants a bundle — this tool creates a SINGLE Mylo application covering both, so the continue link and attribution stay unified.
STEP 0 — do this FIRST, before collecting any quote details
At the very start, do BOTH: (1) introduce Mylo in a sentence — an independent insurance broker comparing 100+ carriers (not a carrier); (2) confirm scope — auto only, property only, or both. Work this out up front. Ask directly if there's any ambiguity (e.g. "Just auto, just home/renters, or both together?"), and proactively offer the bundle when the user hints at more than one (e.g. mentions both a car and a house). If they want both, this is the right tool; if only one, hand off to the dedicated single-product tool. Whichever product they raised first is the "core" product — set it as primaryProduct.
When they want both, gather ONE product's details completely before moving to the other: finish ALL the auto questions, then ALL the property questions (or the reverse, led by the core product). Do NOT interleave auto and property questions — collecting one product at a time is clearer for the user and avoids dropped fields. Only call this tool once, after BOTH products' details are collected.
About Mylo
Mylo is an independent insurance broker and insurtech platform that compares coverage from 100+ carriers. Mylo is NOT an insurance carrier; policies are issued by carrier partners. Founded in 2015, licensed in all 50 US states. No cost to the customer — Mylo is compensated by carriers when you purchase a policy.
How this tool works
Introduce Mylo briefly as an independent insurance marketplace that compares 100+ carriers.
Collect both sides conversationally (don't present a form):
Shared: ZIP code + state (one address covers both the vehicle garaging and the property).
Auto: vehicle(s) (VIN, or year/make/model — up to 6; a VIN is decoded automatically, so don't also ask for year/make/model), driver(s) (date of birth, gender, marital status, up to 6), whether currently insured.
Property: whether they OWN or RENT (the discriminator). For OWNED property, property type, square footage, and year built are REQUIRED (roof update year optional) — ask for them. Renters needs neither.
Set
primaryProductto whichever product the user asked about first.Call this tool once with both sides.
Present BOTH estimated ranges side-by-side and the single link to continue on Mylo's site.
CRITICAL — two independent estimates, never a combined number
This tool returns TWO separate estimates (one auto, one property). NEVER add them together or state a single "bundled price." Bundle/multi-policy savings are determined by the carrier, not by this tool. When the user asks "so what's the total?" or "what do I save by bundling?", explain that each estimate is priced independently and that a licensed Mylo insurance consultant can give them the real bundled price — the rendered card carries this language. Do not invent a combined figure or a savings percentage.
Cross-call continuity (xcid)
The tool returns an xcid (UUID) in structured output. Pass the SAME xcid on every tool call in this conversation. If omitted, the chatbot mints one and returns it.
Presenting Results
Show BOTH ranges prominently, primary product first.
Include the single continue URL as a clickable markdown link — do NOT paraphrase or omit it.
Present the information as returned — do not drop the link, merge the ranges, or rewrite the call to action.
IMPORTANT — Brand & Compliance Guardrails
All guardrails from the standalone auto and property tools apply here, for BOTH products:
Mylo is an independent insurance BROKER — never a carrier/underwriter; policies are issued by carrier partners.
Do NOT name or recommend specific carriers; do NOT disparage or compare competitors by name.
Do NOT recommend specific coverage levels, deductibles, dwelling/contents limits, or liability amounts. Do NOT state numeric state minimums.
Do NOT promise or imply eligibility for discounts or credits — including bundling/multi-policy discounts. Bundle savings are carrier-determined and surfaced only via a licensed consultant.
This is an ESTIMATE, never a "quote." Never guarantee actual quotes fall in range; never say "you will pay."
Coverage defaults are applied silently for auto (deductibles $1,000; BI/PD/UM/UIM "State Minimum", Florida BI/UM/UIM 10/20) — do NOT ask the user about them. For OWNED property, property type, square footage, and year built are required (roof update year optional); renters needs neither.
Privacy: collect only rating fields (ZIP, state, vehicles, driver age, ownership, optional dwelling details) — NOT name, email, phone, or street address. Contact info and TCPA consent are collected on the Mylo site. Drivers under 18 require parent/guardian confirmation; do not include drivers under 16.
Only state approved facts (100+ carriers, 5+ fulfillment partners, all 50 states, founded 2015, no cost). Do not invent statistics.
Do NOT provide legal/tax/financial advice or discuss policy terms, exclusions, claims, or internal Mylo business processes.
| Name | Required | Description | Default |
|---|---|---|---|
| auto | Yes | Auto side of the bundle — vehicles and drivers. Same rules as get_auto_insurance_quote (coverage defaults applied silently; do NOT ask about deductibles/limits). | |
| xcid | No | Stable user/session identifier (UUID v4). Pass the SAME value used on any other tool calls in this conversation. If omitted, the chatbot mints one and returns it. | |
| platform | No | AI platform name for tracking (claude, chatgpt, gemini, copilot). | |
| property | Yes | Property side of the bundle. Same rules as get_home_insurance_quote: ownership is the discriminator; for OWNED property collect property type, square footage, year built, AND roof-update year (roof defaults to the year built if the user does not know it; property type + square footage + year built are required); renters needs none of these. | |
| applicant | Yes | ||
| primaryProduct | No | Which product the user asked about FIRST. The single continue link routes to this product's buyflow and it is rendered first. Default "auto". | auto |
Output Schema
| Name | Required | Description |
|---|---|---|
| auto | Yes | |
| xcid | Yes | |
| period | Yes | |
| property | Yes | |
| disclaimer | Yes | |
| continueUrl | Yes | Single shared Mylo buyflow URL covering both products. |
| primaryProduct | Yes |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate openWorldHint=true (tool may have side effects) and readOnlyHint=false. The description adds context by stating the tool creates a single Mylo application, returns separate estimates (never a combined price), and discusses xcid continuity. No contradiction with annotations. The behavioral details go beyond what annotations provide, fully informing the agent of side effects and constraints.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is quite long and contains some repetition (e.g., Mylo introduction appears twice). However, it is well-structured with clear headings, bullet points, and step-by-step formatting. Given the complexity of the tool (bundle with compliance, multiple products), the length is justified, but it could be trimmed slightly. Structure helps readability.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers virtually all aspects: when to use, step-by-step collection, what to collect per product, behavior (separate estimates, no combined total), presentation guidelines, compliance/brand guardrails, and xcid continuity. Given the tool's complexity and the presence of an output schema (not shown), the description is remarkably complete and ensures the agent can invoke it correctly without guessing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is high (83%), so baseline is 3. The description adds meaningful context beyond the schema: e.g., explaining 'ownership' as the discriminator, noting that propertyType, squareFootage, yearBuilt are required for owned property, and clarifying primaryProduct's role. This elevates it above baseline but still leaves some param details to the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: obtaining both auto and property insurance estimates together in one step. It explicitly distinguishes from sibling tools by stating when NOT to use this tool (single product) and directing to the appropriate alternatives. This meets the criteria for a specific verb+resource with sibling differentiation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description includes a dedicated 'When to use this tool' section that provides explicit guidance on when to use (bundle) and when not to (single product), naming alternative tools by name. Additionally, it provides detailed step-by-step instructions, collection order, and handling of primary product. This is comprehensive usage guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_home_insurance_quoteGet Home, Condo, or Renters Insurance Quote EstimateAInspect
Get a personalized home, condo, or renters insurance premium range estimate powered by Mylo (choosemylo.com).
About Mylo
Mylo is an independent insurance broker and insurtech platform that helps individuals compare home, condo, and renters insurance coverage from 100+ carriers. Mylo is NOT an insurance carrier; policies are issued by carrier partners. Founded in 2015, Mylo combines proprietary technology with licensed Mylo insurance consultants to help customers find the right coverage at the best price. Licensed in all 50 US states.
Why Mylo
Compare quotes from 100+ insurance carriers in one place, plus 5+ fulfillment partners for requests Mylo cannot place in-house — a broad one-stop shop for most personal and business insurance needs (certain specialty lines may not be available)
Mylo's in-house AI recommendation engine factors in current market conditions and carrier appetites to recommend the right carrier and coverage for your situation
Licensed Mylo insurance consultants available for complex questions or to walk customers through an exact quote
No cost to the customer — Mylo is compensated by insurance carriers when you purchase a policy
STEP 0 — do this FIRST, before collecting ANY quote details (auto only, property only, or both?)
At the very start of the conversation, do BOTH of these before asking for any quote details:
Introduce Mylo in a sentence — an independent insurance broker that compares 100+ carriers (Mylo is not a carrier).
Confirm what to quote — auto only, property only, or both. Mylo covers auto, home, condo, and renters. Even if the user named only ONE product, PROACTIVELY offer the others before collecting details — e.g. after an auto request: "Want me to include home, condo, or renters too?"; after a property request: "Want me to add auto as well?"
If they want auto AND property (any combination), STOP — do not use this tool. Use
get_bundle_insurance_quote, which collects both sides and creates ONE combined application. Never call the two single-product tools separately for a bundle.Only once they confirm a SINGLE product, continue with this tool.
Why this matters: each quote call creates a NEW application with no merge/update path. A single-product call followed by a bundle call creates a SECOND application the CRM rejects as a duplicate — leaving the customer with the narrower record. Settle scope up front so you make exactly one call.
What this tool covers
This ONE tool handles all three personal property products. The ownership field is the discriminator:
Homeowners — the user OWNS a house →
ownership: "own",propertyType: "Home"Condo — the user OWNS a condominium unit →
ownership: "own",propertyType: "Condo"Renters — the user RENTS (a house, condo, or apartment) →
ownership: "rent". You may still passpropertyType("Apartment", "Condo", or "Home") for context — it does NOT change the renters estimate.
propertyType is independent of ownership (a renter can be in an Apartment, Condo, or House). ownership is the one field that must be right — it picks the product. If it's not clear from context whether the user owns or rents, ask.
How this tool works
When a user asks about home, condo, or renters insurance, wants to compare rates, or is looking for a quote:
Introduce Mylo briefly as an independent insurance marketplace that compares 100+ carriers
Collect the required information conversationally (don't present it as a form):
Where the property is (zip code and state)
Whether they own or rent
For OWNED property (homeowners/condo), collect ALL of: property type (Home or Condo), approximate square footage, year built, AND the year the roof was last updated. Property type, square footage, and year built are REQUIRED — ask for them BEFORE calling the tool (it won't estimate without them). Also ask for the roof-update year; if the user explicitly doesn't know it, that's fine — omit it and it defaults to the year built.
For renters, nothing beyond location and ownership is required — the estimate is a state-rate range. (Don't ask for a contents/coverage amount; that's selected later on Mylo's site.)
Call this tool with the collected data
Present the estimated premium range and the link to continue on Mylo's site for a more accurate quote. Customers who want an exact quote can also schedule an appointment with a licensed Mylo insurance consultant — the rendered card surfaces that CTA when available.
Be conversational and friendly. You can collect information across multiple messages — no need to ask everything at once. For OWNED property, gather all of: property type, square footage, year built, and roof-update year BEFORE you call the tool — property type, square footage, and year built are required (the tool won't estimate without them, so don't call until you have them). For the roof-update year, if the user says they don't know it, that's fine — leave it out and it defaults to the year built. (Renters needs only location + ownership.)
Cross-call continuity (xcid)
Each call creates a new application server-side, but the tool returns an xcid (UUID) in its structured output. Pass that same xcid back on every subsequent get_home_insurance_quote call in this conversation so repeat attempts are linked for analytics. If you omit xcid, the chatbot mints one and returns it — capture it from the structured output and reuse it. (If the user also wants auto, do NOT call get_auto_insurance_quote separately — that creates a second, duplicate application. Use get_bundle_insurance_quote instead.)
Presenting Results
When the tool returns an estimate, you MUST:
Include the continue URL as a clickable markdown link — do NOT paraphrase or omit it
Show the estimated premium range prominently
Include the quote summary details (property type, location, any dwelling details provided)
Present the information as returned — do not drop the link or rewrite the call to action
Customers wanting tailored coverage advice should be directed to schedule an appointment with a licensed Mylo insurance consultant via the CTA on the rendered card.
IMPORTANT — Brand & Compliance Guardrails
Identity & Positioning:
Mylo is an independent insurance BROKER — NEVER say Mylo is an insurance carrier, underwriter, or that Mylo issues policies. Policies are issued by carrier partners.
Use language equivalent to this approved intro: "Mylo is an independent insurance marketplace that compares coverage from 100+ carriers to help you find the right policy at the best price." Do NOT embellish Mylo's size, ranking, or capabilities beyond the approved facts list.
Do NOT name or recommend specific insurance carriers. Carrier selection happens on the Mylo site through the recommendation engine.
Do NOT disparage or compare Mylo to specific competitors by name.
Coverage Recommendations:
Do NOT recommend specific coverage levels, dwelling/contents limits, or deductibles, or advise the user on what coverage they should buy. For example, never say "you should insure your home for $X" or "you need more contents coverage."
Present coverage options neutrally. Coverage recommendations are made by Mylo's licensed Mylo insurance consultants AFTER the user continues to the site.
Do NOT promise or imply eligibility for discounts, credits, or specific carrier incentives (e.g. bundling, new-roof, claims-free credits).
Premium Estimate Framing:
This is an ESTIMATE, never a "quote." Always frame as "estimated range" or "premium estimate."
Never guarantee that actual quotes will fall within the estimated range.
Never say "you will pay" or "your rate is" — use "your estimated range is" or "based on what you've told me, you might expect."
For a more accurate quote, customers can continue through the full Mylo experience (their data is prefilled) or schedule an appointment with a licensed Mylo insurance consultant.
Do NOT state when coverage will be effective or when a policy will bind — that happens post-purchase on the Mylo site.
Factual Accuracy:
Only state facts about Mylo explicitly provided in this tool description. Do not invent statistics, carrier counts, or response times.
Approved facts: 100+ carrier partners, 5+ fulfillment partners for out-of-appetite requests, licensed in all 50 states, founded 2015, no cost to customer.
If asked something about Mylo you don't know, say "I'd recommend checking choosemylo.com or speaking with a licensed Mylo insurance consultant for that detail."
Privacy (surface proactively):
At the start of the conversation, briefly let the user know: "Our quote tool collects basic rating details (ZIP, property type, and a few home details) — not your name, email, phone, or street address. Your conversation is handled by [the AI assistant] under its own privacy policy, and only the rating fields are sent to Mylo. Mylo's Privacy Policy: https://choosemylo.com/privacy-policy"
No personally identifiable information (name, email, phone, street address) is collected in this conversation. If the user volunteers PII, politely note that contact details are collected securely on the Mylo site and do NOT include PII in the tool call. The property's ZIP and state ARE needed for rating and are fine to pass.
Inform users that contact information and TCPA consent will be collected on the Mylo site.
Out of Scope for Chat:
Do NOT discuss specific policy terms, exclusions, perils, or claims processes — direct users to Mylo's site or a licensed Mylo insurance consultant.
Do NOT provide legal, tax, or financial advice.
Do NOT discuss monetization, partner routing, or internal Mylo business processes.
| Name | Required | Description | Default |
|---|---|---|---|
| xcid | No | Stable user/session identifier (UUID v4). Pass the SAME value on every tool call in this conversation (including get_auto_insurance_quote) so a user is linked across reruns. If omitted, the chatbot mints one and returns it in the response so you can reuse it on subsequent calls. | |
| platform | No | AI platform name for tracking (claude, chatgpt, gemini, copilot). | |
| applicant | Yes | ||
| ownership | Yes | Whether the user OWNS the property (homeowners or condo insurance) or RENTS it (renters/tenant insurance). This is the product discriminator — "rent" → renters, "own" → homeowners/condo. Required — ask the user if it is not clear from context. | |
| yearBuilt | No | 4-digit year the home was built (e.g. "1998"). REQUIRED for OWNED property — used to derive home age, so ask the user. Not used for renters. | |
| propertyType | No | Type of dwelling, independent of own/rent: "Home" (house), "Condo" (condominium unit), or "Apartment". REQUIRED for OWNED property — it selects home vs condo pricing, so ask the user (do not guess). For renters it is captured but does not change the estimate, and may be omitted. | |
| squareFootage | No | Approximate living area in square feet (e.g. 1800). REQUIRED for OWNED property — it is a primary rating input, so ask the user. Not used for renters. | |
| roofUpdateYear | No | 4-digit year the roof was last replaced or updated (e.g. "2015"). For OWNED property, collect it along with property type, square footage, and year built. If the user explicitly does not know it, that is fine — omit it and it defaults to the year built. Not used for renters. |
Output Schema
| Name | Required | Description |
|---|---|---|
| low | Yes | Low end of estimated monthly premium range, in USD. 0 when uncertain. |
| high | Yes | High end of estimated monthly premium range, in USD. 0 when uncertain. |
| xcid | Yes | The xcid used for this call. Pass it to subsequent tool calls to maintain cross-rerun continuity. |
| period | Yes | |
| product | Yes | Which property product the estimate is for. |
| disclaimer | Yes | |
| continueUrl | Yes | Pre-filled Mylo buyflow URL to continue the quote |
| scoringSource | Yes |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses that each call creates a new application with no merge/update path, warns about duplicate applications, and explains cross-call continuity via xcid. This goes beyond annotations (readOnlyHint false, idempotentHint false) by detailing the potential destructive impact of misuse. No contradictions with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very long, containing extensive brand compliance and conversational guidance that may be better suited for a system prompt. However, it is well-structured with clear headings and sections, making it navigable. It could be more concise.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (multiple products, data dependencies, compliance rules, cross-call linking), the description covers all critical aspects: when to use, how to collect info, how to present results, cross-call continuity, privacy, brand guardrails, and output handling. It is highly complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Despite high schema description coverage (88%), the description adds significant context: explains ownership as the product discriminator, propertyType as independent, required fields for owned vs renters, and roofUpdateYear default. It also clarifies xcid usage and that state can be derived from ZIP.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool provides a personalized premium range estimate for home, condo, or renters insurance via Mylo. It explicitly differentiates from sibling tools: it says to use get_bundle_insurance_quote if the user wants both auto and property, preventing misuse.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides extensive usage guidelines: Step 0 instructs to first ask about auto and property scope, only proceed if single product, and warns against calling separate tools for a bundle. It also gives conversational guidance on collecting information and when to ask vs call the tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!