Hutsenpiller Insurance: Tennessee Auto, Home, Flood and Life Quotes

Update quote details

update_quote

Adds or changes details on a quote. Objects merge; lists replace whole.

data uses these keys (field_guide lists every accepted field and value):
- applicants: list of every person in the household. Exactly one has relationToInsured INSURED.
  Each needs firstName, lastName, dateOfBirth, sex, maritalStatus; drivers also need isDriver true
  and driverDetails.licenseState. Lists replace whole, so always resend everyone.
- auto: residenceType, priorInsurance, vehicles (list; each needs a vin, or year+make+model+subModel
  from lookup_vehicle, plus ownershipStatus, primaryUse, annualMileage).
- home: coverage.dwellingCoverage (estimated rebuild cost in dollars), property (yearBuilt,
  squareFootage, constructionType, roofMaterial, roofUpdateYear, ...), utilities, underwriting, claims.
- Top level: dateOfBirth, lengthAtCurrentAddress, email, phone, primaryAddress.
Coverage limits are set by the agency and cannot be sent here.
Returns a short summary of what is on file and the remaining missing items.

Input Schema

Name	Required	Description	Default
`data`	Yes
`quote_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 4, 2026

TDQS

A4.2/5.0

Behavior5/5

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

The annotations declare that this tool mutates state (readOnlyHint=false) and is not idempotent, and the description adds the operational detail an agent actually needs: objects merge while lists replace whole, so the entire applicants list must be resent or data will be lost. It also states that coverage limits cannot be set through this call and describes the return value, which is context beyond the annotations.

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?

The description is front-loaded with the most consequential rule (merge-versus-replace semantics) and then organized into scannable bullets by domain. It is dense but nearly every clause carries operational weight; the '...,' ellipses in the home property list are the only slightly loose element.

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?

Given a complex nested free-form payload, no schema descriptions, and no output schema, the definition covers the critical structures, destructive merge behavior, and the shape of the response. It stops short of a full field enumeration, but it delegates that to field_guide by name, which is a reasonable completeness strategy.

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

Parameters5/5

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

The input schema has 0% description coverage and uses a bare free-form 'data' object, so the description must carry the entire burden, and it does. It enumerates the applicant, auto, home, and top-level key structures, including required sub-fields such as relationToInsured INSURED, driverDetails.licenseState, and the vehicle identification rules, and it points to field_guide and lookup_vehicle for lookups.

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?

The description opens with a specific verb and resource: 'Adds or changes details on a quote.' An agent can distinguish this from write-type siblings like submit_quote or start_quote because the scope of 'details' is clear. However, the description never names a sibling or explicitly states how it differs from them.

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?

It gives per-field guidance, such as 'always resend everyone', and one exclusion: 'Coverage limits are set by the agency and cannot be sent here.' It does not say when to call this tool instead of start_quote, submit_quote, or get_quote_status, so the agent must infer the workflow position from the sibling names.

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

All Hutsenpiller Insurance: Tennessee Auto, Home, Flood and Life Quotes 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?