Texasautoquotes

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

A3.8/5.0

Behavior4/5

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

Goes well beyond the minimal annotations (readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false) by disclosing that the licensed contact must confirm by email link, nothing is delivered before confirmation, and the pricing model (free founding period then prepaid credits). 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.

Conciseness4/5

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

Approximately 70 words across 4 sentences, each adding distinct information: purpose, required inputs, confirmation gating, and business terms. Front-loaded with the core action, making the description easy to scan.

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?

Covers the registration workflow, confirmation requirement, and pricing terms, but with no output schema and 12 parameters, the description omits what a successful registration returns (e.g., confirmation status, registration ID) and any failure/error behavior. Adequate for the input side, incomplete on the output side.

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% (4 of 12 parameters lack descriptions: agency_name, website, webhook_url, contact_email). The description re-enumerates required inputs but does not clarify the undocumented parameters meaningfully (especially website and webhook_url), nor fully compensate for the coverage gap.

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?

Clearly states a specific action ('register the agency to receive consented consumer requests in its states') with the resource (an insurance agency as a buyer). Among siblings (agency_status, check_eligibility, pull_requests, request_agent_contact), this is distinctly the registration entry point, leaving no ambiguity about what the tool does.

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?

Describes the intended audience ('For an AI working for a licensed insurance agency') and the registration workflow, but does not explicitly contrast with siblings such as check_eligibility or agency_status, nor state when to prefer this tool over them. Usage context is implied rather than stated.

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

All Texasautoquotes 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 addresses a distinct function—eligibility, quotes, terms, agency registration/status, market data, lead pulling, and contact requests—with no functional overlap. Even the similar request/pull tools are clearly separated by actor and action.

Naming Consistency2/5

Names mix imperative verb-object forms (check_eligibility, get_quotes, register_agency) with noun phrases (agency_status, data_use_terms, market_data) and an ambiguous pull_requests. There is no uniform verb/noun pattern or consistent prefix.

Tool Count5/5

Eight tools is well within the ideal range for this domain and covers both consumer-facing and agency-facing operations without redundancy or bloat.

Completeness3/5

Core quote and lead flows are present, but lifecycle coverage is incomplete: there is no tool to update or disable an agency, revoke consent/opt out, or manage the status of pulled leads. The privacy terms reference revocation but no corresponding action exists.

Resources

Need Help?