Skip to main content
Glama

compare_state_minimums

Compare 2026 minimum auto insurance requirements across US states side by side, or filter for states requiring PIP or uninsured motorist coverage and the highest or lowest liability limits.

Instructions

Compare 2026 minimum auto insurance requirements across multiple US states, or list states requiring PIP or uninsured motorist coverage.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "compare_state_minimums"
  }
}

Input Schema

NameRequiredDescriptionDefault
filterNoOptional preset filter when 'states' is not provided.
statesNoOptional list of state names or 2-letter abbreviations to compare side-by-side.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that this is a comparison/listing operation over 2026 minimum coverage data, but it does not clarify output format, data freshness, authorization needs, or precedence when both states and filter are supplied.

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 description is a single, front-loaded sentence with no wasted wording. It efficiently states the primary comparison purpose and the alternate listing mode.

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?

The tool is simple with two optional parameters, but there are no annotations and no output schema. The description explains the core purpose and modes, yet it leaves gaps around return format, filter precedence, and how to choose this tool over the sibling get_state_minimums.

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 description coverage is 100%, so the schema already documents both parameters and their roles. The description adds useful domain context by mentioning multiple states and PIP/UM state listings, but it does not explain the highest_liability or lowest_liability presets or the optionality/precedence rules beyond what the schema says.

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 states a specific verb and resource: "Compare 2026 minimum auto insurance requirements across multiple US states," with a secondary listing mode for PIP/UM states. It is clear, but it does not distinguish this from the sibling get_state_minimums for single-state lookups.

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?

The description implies when to use the comparison mode versus the listing mode by mentioning multiple states and PIP/UM coverage filters. However, it does not explicitly state when to use this tool instead of get_state_minimums or how the optional states and filter parameters interact in practice.

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