Skip to main content
Glama

mind-of-mylo-quotes

by com.choosemylo

Get Auto + Home/Condo/Renters Bundle Insurance Estimate

get_bundle_insurance_quote

Get BOTH an auto AND a home/condo/renters insurance premium estimate in one step, powered by Mylo (choosemylo.com).

CRITICAL — you MUST call this tool to produce any estimate

You do NOT have Mylo's pricing data and CANNOT compute, infer, recall, or look up an insurance premium yourself. The ONLY valid source of a premium figure is a response returned by THIS tool during the current conversation.

  • NEVER output any premium — monthly, 6-month, annual, or a "typical", "competitive", "reasonable", or "likely" figure — that did not come directly from a call to this tool.

  • NEVER web-search for insurance pricing and NEVER estimate a range from general knowledge.

  • As soon as you have the required inputs, CALL THIS TOOL. Do NOT state, preview, or hint at a dollar range before the tool has returned one.

  • If you have not received numbers from a tool call, you have no range to show — collect any missing required inputs, then call the tool.

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

  1. Introduce Mylo briefly as an independent insurance marketplace that compares 100+ carriers.

  2. 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.

  3. Set primaryProduct to whichever product the user asked about first.

  4. Call this tool once with both sides — this call is REQUIRED to obtain the ranges; never skip it or estimate either range yourself.

  5. ONLY after the tool returns, present BOTH estimated ranges it returned 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 ONLY the numbers the tool returned — never ranges you generated yourself. If you have not called the tool, show no figures.

  • 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
autoYesAuto side of the bundle — vehicles and drivers. Same rules as get_auto_insurance_quote (coverage defaults applied silently; do NOT ask about deductibles/limits).
xcidNoStable 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.
platformNoAI platform name for tracking (claude, chatgpt, gemini, copilot).
propertyYesProperty 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.
applicantYes
primaryProductNoWhich 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

TableJSON Schema
NameRequiredDescriptionDefault
autoYes
xcidYes
periodYes
propertyYes
disclaimerYes
continueUrlYesSingle shared Mylo buyflow URL covering both products.
primaryProductYes

TDQS

A4.7/5.0
Behavior5/5

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

Annotations indicate the tool is not read-only and not destructive, but the description adds substantial behavioral context: it creates a single Mylo application, returns two independent estimates that must not be combined, requires a single xcid, and lays out compliance guardrails. 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.

Conciseness3/5

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

The description is very long (11 paragraphs plus sections), but well-structured with headings, critical warnings, and step-by-step instructions. For a complex tool, the verbosity is somewhat justified, but it could be more concise without losing key guidance.

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 (6 parameters, nested objects, output schema), the description is thorough: covers prerequisites, collection process, cross-call continuity, output presentation, compliance guardrails, and privacy constraints. Output schema exists, so return values are not needed in the description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is high (83%), so the description adds meaningful context beyond the schema: explains how primaryProduct is determined, the order of collection, silent defaults for auto coverage, and the role of property.ownership as a discriminator. It does not invent new parameter info but clarifies usage.

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 the tool's purpose: 'Get BOTH an auto AND a home/condo/renters insurance premium estimate in one step.' It distinguishes from siblings by specifying when to use the bundle tool versus the dedicated auto or property tools, and warns against using two separate tools for a bundle.

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 provides explicit guidance on when to use this tool (when the user wants both auto and property) and when not (only one product). It names the alternative sibling tools directly and cautions against calling single-product tools for a bundle.

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

All mind-of-mylo-quotes toolsInspect
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.6/5.0
Disambiguation4/5

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.

Naming Consistency5/5

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.

Tool Count4/5

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).

Completeness4/5

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.

Resources