Texas 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

A3.8/5.0

Behavior4/5

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

Discloses that confirmation via email link is required before delivery, and mentions the free founding period and prepaid credits. This is key behavioral information beyond the schema.

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?

Description is reasonably concise and front-loaded with the purpose. It uses a clear structure, though it packs many details into a few sentences.

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 covers the registration flow, confirmation requirement, and pricing, but does not elaborate on optional parameters or error handling. It points to /join for terms, suggesting completeness through external reference.

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?

The description explains the core parameters like agency name, NPN, states, contact info, and delivery rail, but omits details on optional fields like website, webhook_url, and verify_token. Schema coverage is 67%, so some parameters lack description in both schema and main description.

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?

States a specific verb 'register' and resource 'insurance agency'. Clarifies the outcome: receive consented consumer requests in its states. No ambiguity about the tool's role.

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?

Provides context that it's for an AI working for a licensed agency, and points to /join for terms. However, it does not explicitly contrast with sibling tools like agency_status or check_eligibility, leaving the 'when to use' somewhat implicit.

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

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

A4.2/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose—eligibility, quotes, contact, market data, agency registration, etc.—with no functional overlap. The descriptions further clarify their unique roles.

Naming Consistency4/5

All tools use lowercase snake_case, which is consistent and readable. Minor deviation exists between verb-based names (e.g., check_eligibility) and noun-based names (e.g., agency_status), but the pattern is largely uniform.

Tool Count5/5

With 8 tools, the set is well within the ideal range and each tool addresses a distinct step in the consumer/agency workflow—from eligibility checks to quote retrieval to lead management.

Completeness4/5

The tools cover the essential consumer-side, agency-side, and data-access operations for an insurance marketplace. A minor gap could be a tool for managing or updating agency information, but the overall coverage is strong.

Resources

Need Help?