Nevadaautoquotes

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

B3.4/5.0

Behavior3/5

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

The description states that confirmation by email is required and that nothing is delivered before confirmation, which is useful. However, it does not clarify idempotency (annotations indicate false), side effects like creation of a pending registration, or whether the registration can be modified later. Given the annotations already indicate non-read-only and destructive=false, the description adds some but not comprehensive transparency.

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 two sentences, front-loaded with the core purpose and then adding confirmation and promotional details. It is concise and avoids redundancy, though the second sentence packs multiple pieces of information (confirmation, free period, prepaid credits) without losing clarity.

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?

Given the 12-parameter schema and no output schema, the description covers the registration flow, confirmation requirement, and commercial terms, which are key context. However, it omits expected return behavior (e.g., what is returned upon successful registration), error scenarios (e.g., invalid NPN, unconfirmed email), and how the 'pull' lead delivery mode works beyond the schema. The pointer to /join for terms partially compensates, but the description is not fully self-sufficient for an agent to anticipate all outcomes.

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

Parameters3/5

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

Schema coverage is 67% (8 of 12 parameters have descriptions). The tool description restates some parameters (agency name, NPN, states, contact name/email/mobile, lead delivery) but adds little beyond the schema. Parameters like website, webhook_url, and contact_email lack elaboration, though the schema provides minimal type info. The description does clarify that contact_email is used for confirmation and contact_phone is US mobile, but overall does not substantially enrich schema semantics.

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), the resource (agency as buyer), and the purpose (receive consented consumer requests). It also provides critical conditions (confirmation required, first agencies free), making the intent unambiguous.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives. Sibling tools like check_eligibility or get_quotes are not referenced, and no conditions for choosing register_agency are given beyond the general purpose. The only directional note is 'Read /join for the terms,' which is more about legal terms than usage selection.

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

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

Disambiguation4/5

Each tool has a distinct primary purpose, but market_data and pull_requests both involve retrieving data records and could be confused without reading descriptions carefully. pull_requests is also semantically ambiguous outside this context.

Naming Consistency3/5

Naming conventions are mixed: some use verb-first patterns (check_eligibility, get_quotes, register_agency, request_agent_contact) while others are noun-phrases (agency_status, data_use_terms, market_data, pull_requests). This is readable but not consistent.

Tool Count5/5

Eight tools is well-suited to the domain: consumer quote flow, agency registration/status, data access, and consent-related operations. No obvious bloat or excessive granularity.

Completeness4/5

The set covers the main journey from eligibility check to quotes to agent contact, plus agency management and market data. However, explicit consent revocation or data deletion is only mentioned inside descriptions rather than exposed as a first-class tool.

Resources

Need Help?