Georgia 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.3/5.0

Behavior5/5

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

The description adds valuable behavioral details beyond the annotations, such as the email confirmation step ('The licensed contact confirms by a link sent to their email; nothing is delivered before that') and the credit model ('The first agencies in a state receive leads free for a founding period, then prepaid credits by card'). These do not contradict the annotations, which only state readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false.

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 a single, largely efficient paragraph. It conveys all essential information without excessive repetition, though it could be slightly more concise by merging some clauses.

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

Completeness4/5

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

There is no output schema, so no return-value explanation is required. The description explains the overall registration flow, the confirmation mechanism, and the billing model, which provides sufficient context for how the tool operates. Minor gaps remain around optional parameters, but they are described in the schema.

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 enumerates the required fields (agency name, NPN, state, states, contact info, delivery method) but does not clarify optional parameters such as website, webhook_url, sms_opt_in, or verify_token. Although the schema descriptions cover 67% of parameters, the description does not compensate for the missing ones, leaving these parameters under-explained.

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 action ('register the agency') and the resource ('insurance agency'), and specifies the purpose: 'to receive consented consumer requests in its states.' This distinguishes it from sibling tools like agency_status or check_eligibility.

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 explicitly targets an AI working for a licensed insurance agency, providing clear context for when this tool is appropriate. It does not explicitly state when to avoid using it, but the purpose is unambiguous and the sibling list is provided in the context, so guidance is adequate.

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

All Georgia 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/5.0

Disambiguation5/5

Each public- to-consumer and agency-facing tool serves a clearly separate step in the workflow: eligibility, quotes, consent, contact, registration, status, queue draining, and data purchase. There is no meaningful overlap between tool purposes.

Naming Consistency4/5

All tool names are snake_case and generally descriptive, but they mix action-oriented names like get_quotes and pull_requests with noun-style resource names like market_data and agency_status. This is a minor consistency deviation rather than a chaotic pattern.

Tool Count5/5

Eight tools cover the platform's distinct functional areas without bloat: consumer quote/contact flow, agency registration and queue management, and data market access. Each tool appears necessary and the total count is well-scoped for the server's purpose.

Completeness4/5

The core workflows are supported end to end: eligibility check leads to quotes, consent leads to agent contact, and agencies can register, check status, and pull routed records. The main gaps are minor administrative operations such as updating agency details or an explicit tool for revoking consent, although POST /forget is referenced.

Resources

Need Help?