Nevada Insurance

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

Behavior4/5

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

The description discloses key behavior beyond annotations: nothing is delivered before email confirmation, there is a founding free period followed by prepaid credits, and optional SMS requires explicit opt-in text. It does not mention all side effects such as account creation details, but the most important gating behavior is described.

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 moderately concise and front-loaded with the core registration purpose, then covers delivery, confirmation, pricing, and terms. It could be trimmed slightly, but every sentence adds relevant setup or gating information.

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

Completeness3/5

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

The description explains the registration process and confirmation requirement, but it does not describe the immediate tool response, return value, or next steps beyond expecting an email link. Given no output schema is provided, more context about what the caller should expect after invoking the tool would improve completeness.

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 explains the main required parameters (agency name, NPN, state, contact info, delivery rail) and some optional behavior (email confirmation, SMS opt-in, webhook/pull). Schema coverage is 67%, and several optional parameters like website and webhook_url are not directly mapped in the prose, but enough meaning is added to guide typical 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 action: register an insurance agency as a buyer to receive consented consumer requests. It distinguishes this tool from siblings like agency_status, get_quotes, and request_agent_contact by focusing on registration and lead delivery setup.

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 explains the intended audience (AI for a licensed insurance agency) and the registration flow, including email confirmation and lead delivery methods. It does not explicitly contrast with request_agent_contact or other sibling tools, but the purpose is clear enough to guide appropriate use.

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

All Nevada Insurance 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.9/5.0

Disambiguation5/5

Each tool targets a clearly distinct function: eligibility checking, quoting, agent contact, agency registration/status/queue, data terms, and market data. The only adjacent pair, agency_status and pull_requests, is cleanly separated by status versus queue draining.

Naming Consistency4/5

Five names use an imperative verb_noun pattern (check_eligibility, get_quotes, register_agency, pull_requests, request_agent_contact), while agency_status, data_use_terms, and market_data are resource-style names. All are lowercase underscore names and still readable, so this is a minor deviation rather than a chaotic mix.

Tool Count5/5

Eight tools is well scoped for a platform covering eligibility, quotes, consumer contact, agency onboarding/status/queue, data terms, and market data. Each tool has a distinct job and none feels redundant.

Completeness4/5

The core journey is covered end to end: check eligibility, get quotes, request agent contact, register an agency, check status, and pull records. Minor gaps exist around agency profile updates/removal and exposing a revoke/forget action as a first-class tool, but agents can complete the main workflows without dead ends.

Resources

Need Help?