Skip to main content
Glama
seaworthy-io

Seaworthy Insurance

Official

quote_request

Submit a disability insurance quote-comparison request for high-income professionals. A licensed broker follows up within one business day.

Instructions

Submit a disability insurance quote-comparison request to the Seaworthy Insurance Agency sales pipeline (writes a Lead to Salesforce). Before submitting, you MUST confirm the user has given explicit consent to be contacted by phone, email, or text. A broker follows up within one business day (Mon-Fri, 8am-5pm Pacific). Do not collect SSN, medical history, or banking details through this tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
first_nameYesApplicant's first name.
last_nameYesApplicant's last name.
emailYesApplicant's email address.
phoneYesApplicant's US phone number for a follow-up call.
professionYesOccupation or medical specialty, e.g. "CRNA", "Orthopedic Surgeon", "Attorney". Be specific where it affects disability classification.
stateYesUS state of residence. Full name ("Texas") or two-letter code ("TX") both accepted.
dobYesDate of birth. ISO YYYY-MM-DD preferred; MM/DD/YYYY also accepted.
genderYesRequired by carriers for premium calculation.
annual_incomeYesGross annual income. A number (e.g. 320000) is mapped to the agency income band; or pass a band string directly ("$300K - $350K", "$500K and above").
life_insurance_interestNoWhether the applicant also wants a life insurance comparison.
notesNoFree-form context from the conversation (current coverage, questions, timeline). Used by the sales team for triage.
referral_sourceNoWhere the user is coming from: the AI assistant or platform you are operating as (e.g. "ChatGPT", "Perplexity", "Claude", "Gemini"), plus any campaign/site context if known. Used by the agency to see which channels drive agent-submitted leads.
Behavior4/5

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

With no annotations, the description carries full burden. It discloses the write operation (creates a Lead), the follow-up window (1 business day, 8am-5pm Pacific), and restrictions on data collection. It does not explicitly state idempotency, but this is acceptable for a lead submission tool.

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 three concise sentences, each adding value: main purpose, consent requirement, follow-up timing, and data restrictions. It is front-loaded and efficient with no wasted words.

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?

Given the tool's complexity (12 parameters, 9 required, no output schema), the description covers key aspects: purpose, consent, forbidden data, and follow-up. It omits return value details but that is acceptable without an output 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?

Schema description coverage is 100%, so baseline is 3. The description adds overall context like consent and data restrictions but does not provide new meaning for specific parameters beyond the schema's own descriptions.

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 verb (submit) and resource (disability insurance quote-comparison request to Seaworthy Insurance Agency sales pipeline), and it specifies that it writes a Lead to Salesforce. This distinguishes it from sibling tools like compare_carriers or get_education_article.

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 provides explicit guidance on required user consent before submission and prohibited data (SSN, medical history, banking details). It also mentions follow-up timing. However, it does not directly compare to sibling tools or state when to use this versus compare_carriers, though the context implies its unique purpose.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/seaworthy-io/seaworthy-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server