Skip to main content
Glama

get_state_minimums

Look up 2026 minimum car insurance liability limits and additional state requirements for any US state or Washington, D.C.

Instructions

Look up 2026 minimum car insurance liability limits and additional state requirements for any US state or Washington, D.C.

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": {
      "state": "<state>"
    },
    "name": "get_state_minimums"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYesUS state name or 2-letter postal abbreviation (e.g., 'Texas', 'TX', 'California', 'DC').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral disclosure. 'Look up' implies a safe read operation, and the description discloses the data vintage (2026) and that additional state requirements are included, but it does not state the data source, whether results are current or cached, or any usage constraints.

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 states the subject, the data year, and the geographic scope immediately.

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?

This is a simple one-parameter lookup with no output schema, and the description adequately states what is looked up and for which jurisdictions. A minor gap is that it does not clarify the shape or scope of 'additional state requirements,' but the core task is clear.

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?

There is one parameter and the schema fully documents it, including acceptance of full state names, two-letter abbreviations, and a DC example. The description adds no parameter meaning beyond the schema, so the baseline 3 for high schema coverage applies.

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 gives a specific verb and resource: looking up 2026 minimum car insurance liability limits and additional state requirements for any US state or DC. It is clear what data is returned, though it does not explicitly distinguish itself from the sibling compare_state_minimums tool.

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?

Usage is implied: call this when you need one state's minimum liability limits and state-specific requirements. There is no explicit when-to-use or when-not-to-use guidance, and no direct routing to the compare_state_minimums alternative.

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