Skip to main content
Glama

Hutsenpiller Insurance: Manage Your Account or Compare Tennessee Quotes

Get policy details

get_policy_details
Read-onlyIdempotent

Current clients only. Details for one policy: vehicles and drivers (auto), insured property (home), premium and term. Driver's license numbers are never returned and dates of birth show the year only.

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>",
      "policy_id": "<policy_id>"
    },
    "name": "get_policy_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
policy_idYes
client_sessionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

The description provides essential behavioral constraints that go beyond annotations, specifically detailing that driver's license numbers are never returned and that dates of birth are truncated to the year only.

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?

The tool definition is extremely efficient. It places the most important usage constraint ('Current clients only') at the start and lists all crucial data types and restrictions in a single, easy-to-digest block of text.

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

Completeness5/5

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

The definition is highly complete despite the lack of an output schema. It thoroughly covers the data scope, the allowed data types, and critical PII masking rules, which is highly necessary for a data retrieval operation of this complexity.

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?

The description focuses entirely on the contents and restrictions of the *output* data, providing no further meaning or format guidance for the *input* parameters (client_session, policy_id) beyond what is implied by their names.

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?

The description clearly identifies the resource (a single policy) and the types of information returned (vehicles, drivers, property, premium, term), distinguishing it from higher-level summary tools in the sibling list.

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?

It provides a clear usage constraint by stating the tool is for 'Current clients only.' This establishes a critical precondition for use, though it does not explicitly contrast its use case against all alternative reporting tools.

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