Skip to main content
Glama

Hutsenpiller Insurance: Manage Your Account or Compare Tennessee Quotes

List my policies

list_my_policies
Read-onlyIdempotent

Current clients only (needs client_session from verify_client_code). Lists the client's active policies with Hutsenpiller Insurance: carrier, line, policy number, term dates and status, with the policy ids the other account tools use.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "client_session": "<client_session>"
    },
    "name": "list_my_policies"
  }
}

Input Schema

NameRequiredDescriptionDefault
client_sessionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare it read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds the meaningful behavioral context that a session from verify_client_code is required and that only active policies are returned. It says nothing about what happens with an expired or unverified session, which is the main remaining gap.

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?

Two compact sentences with the access precondition front-loaded and the return payload enumerated afterward; almost no wasted wording. Slightly dense mid-sentence field list, but it earns its place.

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?

With no output schema, the description usefully enumerates the returned fields and the policy ids, and it explains the one required parameter's origin and the client-eligibility constraint. It leaves pagination/volume limits unaddressed, which matters for a list tool but is a minor omission given the otherwise complete picture.

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 0%, so the description must carry the meaning of client_session, and it does provide the crucial provenance (obtained from verify_client_code). It does not describe format, lifetime, or failure behavior for an invalid session, so it only partially compensates for the coverage gap.

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 resource ('Lists the client's active policies with Hutsenpiller Insurance') and previews the returned fields (carrier, line, policy number, term dates, status, policy ids), which clearly separates it from a detail-oriented sibling like get_policy_details.

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 an explicit precondition ('Current clients only') and names the prerequisite tool that supplies the session ('needs client_session from verify_client_code'), plus hints this is a discovery step whose ids feed 'the other account tools'. It never explicitly says when to prefer get_policy_details or get_coverage_summary instead, so it stops short of full alternative routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources