Skip to main content
Glama

bizinsured

by io.github.jbiggs77
OverviewDiscussionsAdmin

connect_with_agent

Generates a handoff to connect the user with a matched independent agent. Pass recommendation_id from get_carrier_recommendations when you have one, so the agent receives the estimate, and list every coverage the user asked for in risk_profile.desired_coverages, including ones that could not be estimated. Omit user_zip_code unless the user gave a ZIP code; never guess one.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_stateYes
risk_profileYes
user_zip_codeNoBusiness ZIP code. Include only if the user gave it. Never guess or use a placeholder.
recommendation_idNo
recommended_carriersNo
user_contact_preferenceNoeither

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • 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"
+]
  2. Changed2 schema fields changed
    • 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"
+}
  3. Changed1 schema field changed
    • 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"
+}
  4. First observed

TDQS

A4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It usefully discloses that the receiving agent gets the estimate and the full coverage list, but does not say whether this triggers outbound contact, requires user consent, is idempotent, or what happens on failure.

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?

Purpose is front-loaded in the first sentence, followed by three actionable directives. The later sentences are clause-heavy but every clause carries a distinct instruction, so there is little waste.

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 side-effecting handoff tool with a nested schema, no annotations, and no output schema, the description covers the two riskiest inputs but omits the outcome (does the agent contact the user?), how user_state or recommended_carriers should be populated, and which nested risk_profile fields matter.

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

Parameters4/5

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

Schema description coverage is only 17%, so the description must compensate and largely does for the key inputs: it explains recommendation_id's origin, prescribes full coverage enumeration in risk_profile.desired_coverages, and adds a firm never-guess rule for user_zip_code beyond the schema's note. It still leaves user_state, recommended_carriers, user_contact_preference, and most nested risk_profile fields unaddressed.

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 and outcome: 'Generates a handoff to connect the user with a matched independent agent.' It also names the sibling relationship by sourcing recommendation_id from get_carrier_recommendations, so an agent can place this tool in the workflow without opening other schemas.

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 conditional rules: pass recommendation_id 'when you have one,' list every requested coverage even if it could not be estimated, and omit user_zip_code unless the user supplied it. Strong context for invoking correctly, though it never states when this tool should not be used (e.g., user only wants quotes/info).

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

All bizinsured toolsInspect
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