bizinsured

Request a licensed agent

connect_with_agent

Use this only when the user asks to speak with an agent, get real quotes or have their coverage reviewed. Saves a referral with the business details, and the linked estimate when you pass recommendation_id, for review by a licensed agent: the BizInsured team for Ohio businesses, or a partner agent elsewhere when one is available. Returns a bizinsured.ai link where the user can choose to submit contact details. The tool does not contact anyone or request a quote, and nothing is shared with an agent until the user submits that form. Do not ask for names, emails or phone numbers in chat. Each call creates a new referral, so call it once per request.

Input Schema

Name	Required	Description	Default
`user_state`	Yes	Two-letter code of the US state where the business operates, not the user's current location
`risk_profile`	Yes
`recommendation_id`	No	recommendationId from get_carrier_recommendations, when you have one
`user_contact_preference`	No		either

Schema Changelog

Changes observed during successful MCP inspections.

Changed20 schema fields changedSep 29, 2026
- addedInput schema / properties / recommendation_id / description
```
Added value: +"recommendationId from get_carrier_recommendations, when you have one"
```
- removedInput schema / properties / recommended_carriers
```
Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}
```
- addedInput schema / properties / risk_profile / properties / annual_revenue / minimum
```
Added value: +0
```
- addedInput schema / properties / risk_profile / properties / business_description / maxLength
```
Added value: +500
```
- addedInput schema / properties / risk_profile / properties / desired_coverages / description
```
Added value: +"Every coverage the user asked for, including ones BizInsured cannot estimate"
```
- addedInput schema / properties / risk_profile / properties / desired_coverages / items / maxLength
```
Added value: +50
```
- addedInput schema / properties / risk_profile / properties / desired_coverages / items / minLength
```
Added value: +1
```
- addedInput schema / properties / risk_profile / properties / desired_coverages / maxItems
```
Added value: +20
```
- addedInput schema / properties / risk_profile / properties / employee_count / maximum
```
Added value: +1000000
```
- addedInput schema / properties / risk_profile / properties / employee_count / minimum
```
Added value: +0
```
- changedInput schema / properties / risk_profile / properties / employee_count / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / risk_profile / properties / iso_gl_code / pattern
```
Added value: +"^\\d{3,6}$"
```
- addedInput schema / properties / risk_profile / properties / naics_code / description
```
Added value: +"Confirmed NAICS code from classify_business"
```
- addedInput schema / properties / risk_profile / properties / naics_code / pattern
```
Added value: +"^\\d{6}$"
```
- addedInput schema / properties / risk_profile / properties / ncci_wc_code / pattern
```
Added value: +"^\\d{3,6}$"
```
- addedInput schema / properties / risk_profile / properties / vertical / maxLength
```
Added value: +50
```
- addedInput schema / properties / risk_profile / properties / years_in_business / maximum
```
Added value: +300
```
- addedInput schema / properties / risk_profile / properties / years_in_business / minimum
```
Added value: +0
```
- addedInput schema / properties / user_state / description
```
Added value: +"Two-letter code of the US state where the business operates, not the user's current location"
```
- removedInput schema / properties / user_zip_code
```
Removed value: -{
-  "description": "Business ZIP code. Include only if the user gave it. Never guess or use a placeholder.",
-  "pattern": "^\\d{5}(-\\d{4})?$",
-  "type": "string"
-}
```

Changed3 schema fields changedSep 25, 2026

addedInput schema / properties / user_zip_code / description

Added value: +"Business ZIP code. Include only if the user gave it. Never guess or use a placeholder."

addedInput schema / properties / user_zip_code / pattern
```
Added value: +"^\\d{5}(-\\d{4})?$"
```

changedInput schema / required

Previous value: -[
-  "risk_profile",
-  "user_state",
-  "user_zip_code"
-]New value: +[
+  "risk_profile",
+  "user_state"
+]

Changed2 schema fields changedSep 22, 2026

addedInput schema / properties / risk_profile / properties / current_carrier
```
Added value: +{
+  "maxLength": 200,
+  "type": "string"
+}
```

addedInput schema / properties / risk_profile / properties / current_policy_expiration

Added value: +{
+  "description": "When the current policy expires or renews (YYYY-MM-DD), if known. Omit dates more than 365 days past or 730 days ahead",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}

Changed1 schema field changedSep 13, 2026

addedInput schema / properties / recommendation_id

Added value: +{
+  "format": "uuid",
+  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+  "type": "string"
+}

First observedMar 31, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Adds rich behavior beyond the annotations: each call creates a new referral (reinforcing idempotentHint=false), the tool does not itself contact anyone or request a quote, and nothing is shared until the user submits the returned form. These are non-obvious lifecycle facts that annotations cannot convey.

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?

Front-loaded with the routing condition and constraint, and every sentence carries weight (behavior, prerequisites, restrictions). Slightly dense and multi-clause, but no filler.

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?

With no output schema, the description correctly explains the return value (a bizinsured.ai link where the user submits contact details) and the full side-effect profile. For a nested-parameter, non-idempotent write tool, an agent has everything needed to invoke it correctly.

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 coverage is 50%, so the description carries partial burden. It clarifies recommendation_id's effect ('the linked estimate when you pass recommendation_id') which is genuinely beyond the schema, but says nothing about the risk_profile object's many fields. Baseline 3 is appropriate given the schema documents the key enum and state fields itself.

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 states a specific verb+resource (saves a referral for review by a licensed agent, returns a bizinsured.ai link) and clearly separates this from siblings by defining the outcome. An agent can distinguish it from get_carrier_recommendations and classify_business without opening any schema.

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?

Explicitly states when to use it ('only when the user asks to speak with an agent, get real quotes or have their coverage reviewed'), names the upstream dependency (recommendation_id from get_carrier_recommendations), and gives operational constraints ('call it once per request', don't ask for names/emails/phones). This is true when/when-not guidance.

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

All bizinsured tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?