Skip to main content
Glama

Commercial Insurance Broker (Property & GL)

Request an AI agent liability insurance quote

request_ai_liability_quote
Destructive

Submits a quote request for AI agent liability insurance (Tech E&O + AI coverage) for a US company headquartered in CA, TX, IL, WI, LA. A licensed broker rates it and emails the quote to the company contact, usually the same business day. Free. Each call creates a real quote request that a human broker works on, using the company details provided. It does not bind coverage.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company_name": "<company_name>",
      "contact_name": "<contact_name>",
      "contact_email": "<contact_email>",
      "state": "<state>",
      "annual_revenue": "<annual_revenue>",
      "ai_agentic_tier": "<ai_agentic_tier>"
    },
    "name": "request_ai_liability_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipNo
cityNo
limitNoTech E&O limit wanted (default 1000000).
notesNo
stateYesState of the company's headquarters.
streetNo
websiteNoCompany website.
retentionNoRetention / deductible per claim (default 10000).
ai_sublimitNoAI coverage sublimit (default 1000000; cannot exceed limit).
company_nameYesLegal name of the company to be insured.
contact_nameYesName of the human at the company who will receive the quote.
prior_claimsNoAny Tech E&O or AI-related claims, regulatory actions or cease-and-desist letters in the last 3 years?
contact_emailYesEmail the quote is sent to.
contact_phoneNo
annual_revenueYesAnnual gross revenue in USD (estimate is fine).
ai_agentic_tierYesHow autonomously the AI acts.
ai_company_typeNo
current_insuranceNoCurrent Tech E&O / cyber carrier and expiration date, if any.
ai_model_providersNo
requested_by_agentNoName of the AI agent or platform submitting this request.
ai_coverage_optionsNoAI coverage parts wanted (default: all).
ai_training_approachNo
what_the_product_doesNoPlain description of the product and what the AI/agent does for customers.
ai_governance_controlsNo
ai_high_stakes_domainsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already flag a non-read-only, open-world, non-idempotent, destructive operation; the description adds real value on top by disclosing that a human licensed broker works the request, that the quote is emailed to the contact, and that each call generates a separate real request. That last point is the key non-idempotency warning. It does not discuss rate limits or duplicate suppression beyond the implication.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

Front-loaded with the core action and eligibility, which is good, but the human-broker point is stated twice ('A licensed broker rates it' and 'a human broker works on'), and 'Free.' as a standalone fragment is terse but weakly integrated. Tightening the broker sentences would recover a point.

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?

For a 25-parameter mutation with an output schema and rich annotations, the description covers outcome, cost, timing, and non-binding status adequately, but leaves the large and partly undocumented input surface unaddressed. An agent still has to rely entirely on the schema for field interpretation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 25 parameters at 60% schema description coverage, roughly ten fields carry no documented meaning anywhere, and the description explains none of them individually — it only refers generically to 'the company details provided.' The only parameter-adjacent fact it adds (eligible headquarters states) is already enforced by the state enum in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Submits a quote request for AI agent liability insurance (Tech E&O + AI coverage)' and scopes it to a US company headquartered in five named states. It implicitly separates itself from sibling info/estimate tools by stressing that a real quote request is created for a human broker, though no sibling is named explicitly.

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?

Gives usable context for deciding to call: eligibility (HQ in CA, TX, IL, WI, LA), cost ('Free'), turnaround ('usually the same business day'), and an outcome limit ('It does not bind coverage'). It stops short of explicitly routing the agent to alternatives such as an estimate or coverage-info tool first.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources