Skip to main content
Glama

Washington State Department of Licensing registered

auto_data_wa_gov_electric_vehicle
Read-only

Washington State Department of Licensing registered electric vehicles (BEV and plug-in hybrid): make, model, model year, EV type, electric range, city, county and ZIP. Vehicles are registrations, not current status; the range field is 0 where not yet researched. Related tools on this server, for a different need: auto_carsdirect_vehicle when you need CarsDirect used-car listings near a US ZIP code: vehicle; auto_fipe_brazil_vehicle_prices when you need Brazilian FIPE reference price for one car: brand, model. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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

Input Schema

NameRequiredDescriptionDefault
cityNoCity name, letters and spaces, 2 to 60 characters (optional)
limitNoMax vehicles, 1 to 100 (default 10)

Output Schema

NameRequiredDescriptionDefault
countNo
sourceNo
vehiclesNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Beyond readOnlyHint and openWorldHint, the description discloses two substantive data caveats — records are registrations rather than current vehicle status, and the range field is 0 where not yet researched — plus a cost model ($0.002 per successful call via x402/USDC across multiple networks) with the notable guarantee that failed calls are not charged. That cost and failure-billing detail is exactly the kind of context annotations cannot express. It stops short of rate limits or pagination behavior.

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 data domain and returned fields, then caveats, then alternatives, then pricing — a sensible information order. The sibling-routing clause is somewhat tangential filler for a tool whose main job is a straightforward data pull, but overall no sentence is redundant.

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?

An output schema exists, so return-value explanation is unnecessary and the description correctly focuses on what the agent cannot see elsewhere: the registration-vs-status caveat, the zero-range convention, and the paid-call billing terms. For a two-optional-param read-only lookup, nothing essential to correct invocation is missing.

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%, with both city (2-60 characters, optional) and limit (1-100, default 10) fully documented in the schema. The description adds no syntax, filtering semantics, or default behavior beyond that, so the baseline 3 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 names a specific verb-less but concrete resource — Washington DOL electric vehicle registrations (BEV and plug-in hybrid) — and enumerates the fields returned: make, model, model year, EV type, electric range, city, county, ZIP. That is far more specific than the title alone. It does not, however, distinguish itself from its closest plausible sibling (auto_ev_database), instead routing to two unrelated tools, so an agent still has to guess at the EV-specific boundary.

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 by the data domain disclosure rather than stated: an agent can infer 'use this for Washington State EV registration data.' The description does route to two alternatives (auto_carsdirect_vehicle, auto_fipe_brazil_vehicle_prices) with explicit conditions, but both are for unrelated needs, so it gives no when-not guidance against the tools it most overlaps with.

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