Skip to main content
Glama

State rules for buying a car

state_rules
Read-onlyIdempotent

A state's car-buying rules: the dealer doc-fee cap or rule, sales tax (state rate, local add-on range, any cap), whether a trade-in lowers the taxed price, how a maker's rebate is taxed, and cancellation rights where on file. Each comes with its source, as-of date and confidence, plus the link to the state's page. Use it for the rules themselves; for a price with a city's local tax, use out_the_door.

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": "state_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYesTwo-letter state code, like PA

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds modest value by disclosing that each datum carries a source, as-of date and confidence, and that cancellation rights exist only 'where on file' — implying spotty coverage. It does not, however, say how gaps are represented in the response or what happens for a state with no record.

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?

Front-loaded with the returned fields, then the routing alternative at the end — a sensible order. The enumerative first sentence is long and dense, but nearly every item earns its place by telling the agent what will and won't be returned; still, it could be trimmed slightly without loss.

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?

There is no output schema, so the description carries the burden of describing return values — and it does, listing each field plus provenance metadata and a link. With one required parameter and annotations covering the safety profile, an agent has everything needed to call this correctly.

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 100% and the single 'state' parameter is fully documented with its two-letter pattern and example 'PA', so the schema does the work. The description adds nothing about the parameter itself; baseline 3 applies when only one parameter exists and it is fully specified in the schema.

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?

Names the resource precisely ('a state's car-buying rules') and enumerates exactly what data comes back: doc-fee cap, sales tax components, trade-in treatment, rebate taxation, cancellation rights. It also names the sibling it is not (out_the_door), so an agent can separate the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The final clause is an explicit routing rule: 'Use it for the rules themselves; for a price with a city's local tax, use out_the_door.' That covers both when to use this tool and which alternative to pick instead.

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