Oklahoma 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.9/5.0

Behavior5/5

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

The annotations indicate a non-read-only, non-idempotent, non-destructive operation. The description adds valuable behavioral details: the confirmation by link, that nothing is delivered before confirmation, the free founding period and prepaid credits (implying billing side effects), and the specific consent text for SMS. These go beyond the raw annotations to explain real-world consequences.

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?

The description is a single, well-organized paragraph with no fluff. It front-loads the purpose, lists the required information, explains the confirmation process, and includes billing/terms context. Every sentence serves a purpose, making it concise yet information-dense.

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

Completeness5/5

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

Given the complexity of registration (confirmation, multiple delivery methods, billing), the description covers all essential steps: what is needed, how leads arrive, the confirmation gate, and the pricing model. There is no output schema, so return values are not required. The description is complete enough for an agent to understand the full context of calling this tool.

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 schema covers 67% of parameters, and the description adds meaningful context for most key fields: it explains that NPN is digits only, contact_name is the licensed contact, contact_phone is a US mobile, and rail describes lead delivery methods. Some optional parameters like website, verify_token, and sms_opt_in are not mentioned in the main description, but the schema descriptions cover them, so the gap is minor.

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 tool's purpose: to register an insurance agency as a buyer to receive consented consumer requests. The verb 'register' is specific, and the description distinguishes it from siblings like check_eligibility, get_quotes, and pull_requests by focusing on the registration workflow and the confirmation step.

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

Usage Guidelines5/5

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

The description explicitly states when to use the tool: when an AI works for a licensed insurance agency and needs to register to receive leads. It also mentions prerequisites (NPN, state, contact info) and the confirmation requirement, making it clear that registration is the first step before lead delivery. The 'Read /join for the terms' reference further clarifies the context.

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

All Oklahoma 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 targets a distinct function—eligibility, quotes, registration, status, data access, contact requests, and queue draining. Descriptions are specific enough to prevent confusion; even related tools like check_eligibility and get_quotes are clearly separated by their purposes.

Naming Consistency4/5

All tool names use snake_case, but they mix verb-noun patterns (check_eligibility, get_quotes) with noun-only patterns (agency_status, market_data). This is readable and mostly predictable, but not fully consistent across the set.

Tool Count5/5

8 tools is well-scoped for an insurance lead-generation server covering quotes, agency management, data access, and consent workflows. Each tool has a clear purpose and none are redundant.

Completeness4/5

The surface covers the core lifecycle: eligibility, quotes, contact requests, agency registration, status checks, data pulls, and data-use terms. Minor gaps exist—no update/delete for agencies, no specific quote retrieval—but agents can work around these for typical workflows.

Resources

Need Help?