bizinsured

Suggest coverages

suggest_coverages

Read-onlyIdempotent

Use this when the user asks which commercial insurance coverages their business needs. Returns coverages ranked essential, recommended or optional, each with a reason, based on the confirmed class codes and the facts the user stated. Pass naics_code and iso_gl_code from classify_business after the user confirms them, and leave out facts the user did not give. Returns no prices; use get_carrier_recommendations for estimates.

Input Schema

Name	Required	Description
`state`	Yes	Two-letter code of the US state where the business operates, not the user's current location
`vertical`	No	topMatch.vertical from classify_business; derived from the class codes when omitted
`naics_code`	No	Confirmed NAICS code from classify_business
`iso_gl_code`	No	Confirmed ISO GL code. For NAICS 531110 it separates 1-4 family rentals (63010) from apartment buildings (60010).
`serves_food`	No
`has_vehicles`	No
`does_delivery`	No
`employee_count`	No
`serves_alcohol`	No
`business_description`	Yes	The business activity, as confirmed with classify_business
`handles_customer_data`	No
`has_physical_location`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedSep 29, 2026
- addedInput schema / properties / business_description / description
```
Added value: +"The business activity, as confirmed with classify_business"
```
- addedInput schema / properties / business_description / maxLength
```
Added value: +500
```
- addedInput schema / properties / business_description / minLength
```
Added value: +2
```
- 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 / iso_gl_code / pattern
```
Added value: +"^\\d{3,6}$"
```
- addedInput schema / properties / naics_code / description
```
Added value: +"Confirmed NAICS code from classify_business"
```
- addedInput schema / properties / naics_code / pattern
```
Added value: +"^\\d{6}$"
```
- addedInput schema / properties / state / description
```
Added value: +"Two-letter code of the US state where the business operates, not the user's current location"
```
- addedInput schema / properties / vertical / description
```
Added value: +"topMatch.vertical from classify_business; derived from the class codes when omitted"
```
- addedInput schema / properties / vertical / maxLength
```
Added value: +50
```

Changed1 schema field changedSep 22, 2026

addedInput schema / properties / iso_gl_code

Added value: +{
+  "description": "Confirmed ISO GL code. For NAICS 531110 it separates 1-4 family rentals (63010) from apartment buildings (60010).",
+  "type": "string"
+}

First observedMar 31, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely useful behavior: it derives results from confirmed class codes plus stated facts, and explicitly returns no prices. It doesn't cover latency or whether omitted facts degrade ranking quality, keeping it short of a 5.

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?

Four sentences, front-loaded with the trigger condition, then inputs, then exclusions, then the sibling redirect. No repetition of schema or name and nothing wasted.

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?

For a read-only 12-param tool with no output schema, the description covers trigger, input sourcing, and that the return is a ranked list with reasons. It does not explain how ranking changes with optional facts, but nothing critical for a correct invocation is missing.

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 only 42% across 12 params, so the description must compensate. It clarifies sourcing for naics_code/iso_gl_code and instructs omission of unstated facts, but says nothing about employee_count, serves_alcohol, has_vehicles, or other booleans that drive ranking. Partial compensation only.

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?

States a specific verb (suggest) and resource (commercial insurance coverages) and describes the output shape: rankings of essential/recommended/optional, each with a reason. An agent can distinguish it from get_carrier_recommendations, which is explicitly named as the pricing alternative.

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?

Explicit when-to-use trigger ('user asks which coverages their business needs'), what to pass (naics_code and iso_gl_code from classify_business, after confirmation), what to omit (facts the user did not give), and which sibling to use instead for prices. Nothing is left to inference.

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?