Flautoquotes

Register an insurance agency as a buyer

register_agency

For an AI working for a licensed insurance agency: register the agency to receive consented consumer requests in its states. Needs the agency name, the producer NPN (National Producer Number) and its state, the states it is appointed in, the licensed contact's name, email and mobile, and how leads should arrive (email, webhook, or pull by key). The licensed contact confirms by a link sent to their email; nothing is delivered before that. The first agencies in a state receive leads free for a founding period, then prepaid credits by card. Read /join for the terms.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`npn`	Yes	NPN (National Producer Number). Your NPN is on your licence and at nipr.com. Digits only.
`rail`	No	How leads arrive: email, an https webhook (HMAC-signed), or pull by key over MCP/REST	email
`states`	No	Two-letter states the agency is appointed in; defaults to npn_state
`website`	No
`npn_state`	Yes	Two-letter state that issued the licence
`sms_opt_in`	No	Optional. true only if the agency contact expressly agrees to this exact text: I agree to receive recurring operational text messages from CoverIntent by TheChattyAI about my agency account and consented lead deliveries. Message frequency varies. Message and data rates may apply. Reply HELP for help or STOP to cancel. Consent is not a condition of registering or buying.
`agency_name`	Yes
`webhook_url`	No
`contact_name`	Yes	The licensed contact, who confirms by email
`verify_token`	No	Optional: from POST /v1/verify/check after the contact enters the code texted to them
`contact_email`	Yes
`contact_phone`	Yes	US mobile

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedSep 7, 2026

addedInput schema / properties / sms_opt_in

Added value: +{
+  "default": false,
+  "description": "Optional. true only if the agency contact expressly agrees to this exact text: I agree to receive recurring operational text messages from CoverIntent by TheChattyAI about my agency account and consented lead deliveries. Message frequency varies. Message and data rates may apply. Reply HELP for help or STOP to cancel. Consent is not a condition of registering or buying.",
+  "type": "boolean"
+}

First observedSep 6, 2026

TDQS

A4.1/5.0

Behavior4/5

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

The description goes beyond annotations by explaining the confirmation process ('nothing is delivered before that'), the free founding period, and the HMAC-signed webhook. It does not contradict the readOnlyHint false annotation.

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 a single paragraph that front-loads the purpose and includes necessary details. It is somewhat verbose due to repeating schema information but remains clear and structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers registration requirements, confirmation step, and terms reference, which is sufficient for the complexity. It doesn't specify output/return value, but no output schema exists, so that's acceptable.

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?

The description repeats the key parameters from the schema and adds context about their purpose (e.g., NPN, states, lead delivery method). It also explains the confirmation flow. Since schema coverage is 67%, the description supplements some but not all parameters (e.g., website, webhook_url are not covered).

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: register an insurance agency to receive consented consumer requests in its states. It includes the specific action and target, distinguishing it from siblings like get_quotes or market_data.

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

Usage Guidelines3/5

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

The description provides context ('For an AI working for a licensed insurance agency') but does not explicitly mention alternative tools or when not to use this one. It implies usage for initial registration but doesn't guide against using other tools.

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

All Flautoquotes 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

A3.8/5.0

Disambiguation5/5

Each tool maps to a distinct job: eligibility, quoting, consent/terms, agency registration, status, lead pull, market data, and contact request. The two data-delivery tools (market_data and pull_requests) are clearly separated by de-identified versus consented/identified content.

Naming Consistency3/5

Five tools follow an imperative verb_noun style (check_eligibility, get_quotes, pull_requests, register_agency, request_agent_contact), while three are noun-only resource names (agency_status, data_use_terms, market_data). All are readable snake_case, but the verb/noun split prevents a single predictable pattern.

Tool Count5/5

Eight tools cover both consumer-facing and agency-facing sides of the quote/contact platform without redundancy. Each tool has a distinct role, and the count is squarely in the well-scoped range.

Completeness4/5

The core lifecycle is covered: eligibility, quotes, consent, agency registration, status, lead delivery, and market data. Gaps are update/delete or revocation operations (e.g., POST /forget is referenced but not exposed as a tool, and agency details cannot be updated), but agents can complete the main workflows.

Resources

Need Help?