Skip to main content
Glama

PolicyVera insurance quotes

Find a car's VIN from its license plate

find_vehicle_by_plate
Read-only

PolicyVera's own plate lookup: the plate and the state that issued it return the VIN with the year, make, model and trim, for vehicles[line][].vin. Cars only. The VIN itself is needed only when the plate cannot be found.

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

Input Schema

NameRequiredDescriptionDefault
plateYesThe plate's letters and numbers.
stateYesThe two-letter state that issued the plate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real value beyond that: it identifies the lookup as PolicyVera's own source, enumerates the returned fields, gives the response path, and restricts scope to cars — though it says nothing about rate limits, failure behavior, or what happens on a miss.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded in the first clause, which is good. But the final sentence is cryptic and its referent ('the VIN itself') is unclear, so it costs space without earning it, and the 'Cars only' fragment sits awkwardly mid-paragraph.

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?

With no output schema, the description usefully carries the return shape (VIN, year, make, model, trim) and the response path, and it states the vehicle-type limit. What remains missing is what happens when the plate is not found, which matters for a lookup tool flagged openWorldHint=true.

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%, with both parameters documented and the state constrained by an enum, so the baseline is 3. The description only restates that the plate and its issuing state are required and adds no format, normalization, or casing guidance beyond the schema.

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 and resource — a plate plus issuing state returns a VIN plus year, make, model and trim — and even points at the response path vehicles[line][].vin. It labels itself 'PolicyVera's own plate lookup', which signals it is the in-house source rather than an external one, though no sibling is named because none exists for this lookup.

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?

'Cars only' is a genuine scope exclusion that tells the agent not to use it for motorcycles or trailers. However, the closing sentence, 'The VIN itself is needed only when the plate cannot be found', is ambiguous — it reads as guidance about when a VIN is required downstream rather than when to call this tool, and no alternative lookup is offered.

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