Californiacarquotes

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
`handoff`	No	Optional standing order. When true, and the licence record places this agency in a city we publish, the agency becomes the one agency a consumer in that city is handed to by name: it is named in the consumer's consent before consent is given, and it receives that record alone rather than sharing it. Nothing is owed until the agency accepts a handoff, and an accepted one is $25. It is not exclusive and it is not a purchase.
`website`	No
`npn_state`	Yes	Two-letter state that issued the licence
`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 / handoff

Added value: +{
+  "default": false,
+  "description": "Optional standing order. When true, and the licence record places this agency in a city we publish, the agency becomes the one agency a consumer in that city is handed to by name: it is named in the consumer's consent before consent is given, and it receives that record alone rather than sharing it. Nothing is owed until the agency accepts a handoff, and an accepted one is $25. It is not exclusive and it is not a purchase.",
+  "type": "boolean"
+}

Changed2 schema fields changedSep 7, 2026

changedInput schema / properties / rail / enum

Previous value: -[
-  "email",
-  "webhook",
-  "pull",
-  "sms"
-]New value: +[
+  "email",
+  "webhook",
+  "pull"
+]

removedInput schema / properties / sms_opt_in

Removed 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"
-}

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?

Annotations cover read-only/destructive safety, and the description adds meaningful behavior beyond that: the licensed contact must confirm via a link sent by email, nothing is delivered before confirmation, and there is a free founding period followed by prepaid credits. It also points to /join for terms. No contradiction 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.

Conciseness5/5

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

Three sentences, each earning its place: audience/action first, then required data, then confirmation and commercial terms. The content is dense but not bloated, and the most important framing comes first.

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?

For a 12-parameter tool with no output schema, the description covers the registration flow, confirmation requirement, lead delivery gating, pricing model, and terms pointer. Minor omissions are the lack of an explicit success return value and no mention of the optional handoff parameter, though the schema thoroughly documents handoff.

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 enumerates the key parameters: agency name, NPN and state, appointed states, licensed contact's name/email/mobile, and lead delivery mode matching the rail enum. It partially compensates for the 67% schema coverage by naming required fields that lack schema descriptions. Optional parameters like handoff, website, webhook_url, and verify_token are left to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the core action: 'register the agency to receive consented consumer requests in its states' and identifies the intended audience: 'For an AI working for a licensed insurance agency.' This is distinct from sibling tools like agency_status or pull_requests, though it does not explicitly name alternatives.

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?

The description makes clear when this tool is appropriate: when an AI representing a licensed agency needs to register that agency to receive consented requests. It does not explicitly state exclusions or name alternative tools, but no sibling tool serves the same registration purpose.

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

All Californiacarquotes 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.

Resources

Need Help?