bizinsured

get_carrier_recommendations

Returns carrier matches and market budget estimates. Supply confirmed classification and actual exposures. Missing inputs, unsupported terms and partial coverage are returned explicitly. State-fund WC is returned separately in stateFundEstimates, including an Ohio BWC estimate from published rates that is not a BWC quote.

Input Schema

TableJSON Schema

Name	Required	Description
`city`	No
`state`	Yes
`source`	No
`zip_code`	No
`naics_code`	No
`deductibles`	No
`has_alcohol`	No
`iso_gl_code`	No
`serves_food`	No
`has_delivery`	No
`prior_losses`	No
`vehicle_count`	No
`vehicle_types`	No
`annual_payroll`	No	Actual annual payroll; never infer from revenue
`annual_revenue`	Yes
`building_value`	No
`effective_date`	No
`employee_count`	No
`square_footage`	No
`coverage_limits`	No
`current_carrier`	No
`payroll_by_class`	No	Actual payroll split by state and workers compensation classification
`desired_coverages`	Yes
`years_in_business`	No
`prior_loss_details`	No
`experience_modifier`	No
`business_description`	No
`business_property_value`	No
`current_policy_expiration`	No	When the current policy expires or renews (YYYY-MM-DD), if known. Omit dates more than 365 days past or 730 days ahead

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 22, 2026

addedInput schema / 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"
+}

Changed37 schema fields changedSep 13, 2026

addedInput schema / properties / annual_payroll

Added value: +{
+  "description": "Actual annual payroll; never infer from revenue",
+  "maximum": 1000000000000,
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / annual_revenue / maximum
```
Added value: +1000000000000
```
addedInput schema / properties / annual_revenue / minimum
```
Added value: +0
```

addedInput schema / properties / building_value

Added value: +{
+  "maximum": 1000000000000,
+  "minimum": 0,
+  "type": "number"
+}

removedInput schema / properties / business_description / default
```
Removed value: -""
```
addedInput schema / properties / business_description / maxLength
```
Added value: +4000
```

addedInput schema / properties / business_property_value

Added value: +{
+  "maximum": 1000000000000,
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / city

Added value: +{
+  "maxLength": 200,
+  "type": "string"
+}

addedInput schema / properties / coverage_limits

Added value: +{
+  "additionalProperties": {
+    "maxLength": 100,
+    "minLength": 1,
+    "type": "string"
+  },
+  "propertyNames": {
+    "enum": [
+      "BOP",
+      "GL",
+      "WC",
+      "commercial_auto"
+    ],
+    "type": "string"
+  },
+  "type": "object"
+}

addedInput schema / properties / current_carrier

Added value: +{
+  "maxLength": 200,
+  "type": "string"
+}

addedInput schema / properties / deductibles

Added value: +{
+  "additionalProperties": {
+    "maximum": 1000000000000,
+    "minimum": 0,
+    "type": "number"
+  },
+  "propertyNames": {
+    "enum": [
+      "BOP",
+      "GL",
+      "WC",
+      "commercial_auto"
+    ],
+    "type": "string"
+  },
+  "type": "object"
+}

addedInput schema / properties / desired_coverages / maxItems
```
Added value: +20
```
addedInput schema / properties / desired_coverages / minItems
```
Added value: +1
```

addedInput schema / properties / effective_date

Added value: +{
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}

removedInput schema / properties / employee_count / default
```
Removed value: -1
```
addedInput schema / properties / employee_count / maximum
```
Added value: +1000000
```
addedInput schema / properties / employee_count / minimum
```
Added value: +0
```
changedInput schema / properties / employee_count / type
```
Previous value: -"number"New value: +"integer"
```

addedInput schema / properties / experience_modifier

Added value: +{
+  "exclusiveMinimum": 0,
+  "maximum": 10,
+  "type": "number"
+}

addedInput schema / properties / iso_gl_code / pattern
```
Added value: +"^\\d{3,6}$"
```
addedInput schema / properties / naics_code / pattern
```
Added value: +"^\\d{6}$"
```

addedInput schema / properties / payroll_by_class

Added value: +{
+  "description": "Actual payroll split by state and workers compensation classification",
+  "items": {
+    "properties": {
+      "class_code": {
+        "pattern": "^\\d{1,6}$",
+        "type": "string"
+      },
+      "class_system": {
+        "maxLength": 30,
+        "minLength": 1,
+        "type": "string"
+      },
+      "payroll": {
+        "exclusiveMinimum": 0,
+        "maximum": 1000000000000,
+        "type": "number"
+      },
+      "state": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "state",
+      "class_code",
+      "payroll"
+    ],
+    "type": "object"
+  },
+  "maxItems": 100,
+  "minItems": 1,
+  "type": "array"
+}

addedInput schema / properties / prior_loss_details

Added value: +{
+  "maxLength": 4000,
+  "type": "string"
+}

removedInput schema / properties / prior_losses / default
```
Removed value: -false
```
addedInput schema / properties / serves_food
```
Added value: +{
+  "type": "boolean"
+}
```

addedInput schema / properties / source

Added value: +{
+  "maxLength": 50,
+  "type": "string"
+}

addedInput schema / properties / square_footage / maximum
```
Added value: +1000000000000
```
addedInput schema / properties / square_footage / minimum
```
Added value: +0
```
addedInput schema / properties / vehicle_count / maximum
```
Added value: +1000000
```
addedInput schema / properties / vehicle_count / minimum
```
Added value: +0
```
changedInput schema / properties / vehicle_count / type
```
Previous value: -"number"New value: +"integer"
```

addedInput schema / properties / vehicle_types

Added value: +{
+  "items": {
+    "maxLength": 100,
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 50,
+  "type": "array"
+}

removedInput schema / properties / years_in_business / default
```
Removed value: -1
```
addedInput schema / properties / years_in_business / maximum
```
Added value: +300
```
addedInput schema / properties / years_in_business / minimum
```
Added value: +0
```
addedInput schema / properties / zip_code / pattern
```
Added value: +"^\\d{5}(-\\d{4})?$"
```

changedInput schema / required

Previous value: -[
-  "naics_code",
-  "state",
-  "annual_revenue",
-  "desired_coverages"
-]New value: +[
+  "state",
+  "annual_revenue",
+  "desired_coverages"
+]

First observedMar 31, 2026

TDQS

B3.1/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose that missing inputs, unsupported terms, and partial coverage are returned explicitly, and that state-fund WC is separated into stateFundEstimates with a specific Ohio BWC estimate behavior. This adds some behavioral context, but it doesn't cover side effects, rate limits, or other potential behaviors. Given zero annotation coverage, it's a modest disclosure.

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?

Three sentences with no wasted words. It front-loads the main purpose, then adds prerequisite, error handling, and a special case. Each sentence provides distinct value, and the structure is logical and efficient.

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

Completeness2/5

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

For a tool with 29 parameters, no output schema, and no annotations, the description is incomplete. It mentions stateFundEstimates but doesn't describe the overall return structure or what 'carrier matches' entails. It lacks details on how parameters interrelate, optionality, or expected response shape. An agent would be left guessing on many aspects.

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

Parameters1/5

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

Schema description coverage is only 10%, and the description does not compensate. It mentions 'confirmed classification and actual exposures' but doesn't map to specific parameters or explain their meaning. With 29 parameters, the description provides almost no guidance on what values to supply, making it insufficient for effective parameter usage.

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 clear purpose: returns carrier matches and market budget estimates. It also specifies prerequisites (confirmed classification and actual exposures). However, it doesn't explicitly differentiate from sibling tools like suggest_coverages, which might also return coverage recommendations, so it's clear but lacks explicit sibling differentiation.

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

Usage Guidelines3/5

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

Provides a clear prerequisite: supply confirmed classification and actual exposures. It also indicates that missing inputs are handled explicitly. However, it does not mention when to use this tool versus alternatives, nor does it give any exclusions or routing guidance. The usage context is implied rather than explicit.

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?