Skip to main content
Glama

Check window sticker by VIN

check_window_sticker
Read-onlyIdempotent

Use this when the user has a 17-character VIN and wants to know what the vehicle is (year, make, model, trim, engine, drivetrain, body, assembly plant), whether the original factory window sticker (Monroney label) is on file for that VIN, how many recalls were issued for the model, and where to find the paint code. Covers vehicles sold new in the US; original stickers are on file mainly for recent Ford, Lincoln, Jeep, Ram, Dodge, Chrysler, Chevrolet, GMC, Cadillac, Buick, Toyota, Lexus, Hyundai, Kia and Nissan models. It does not return accident, title or ownership history.

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": {
      "vin": "<vin>"
    },
    "name": "check_window_sticker"
  }
}

Input Schema

NameRequiredDescriptionDefault
vinYesThe 17-character Vehicle Identification Number. Letters I, O and Q never appear in a VIN.

Output Schema

NameRequiredDescriptionDefault
vinYes
decodedNo
vehicleYesYear, make, model and trim
details_urlYesThe StickerByVIN result page for this VIN
recalls_for_modelNoRecall campaigns issued for this model and year (not only open ones on this car)
paint_code_locationNo
open_recall_check_urlNoNHTSA's official open-recall check for this exact VIN
original_window_stickerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is settled. The description adds genuinely useful behavior context beyond them: coverage is limited to US-market vehicles and stickers are on file mainly for a named list of makes, which tells the agent when results will be empty or partial.

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?

A single front-loaded sentence that opens with the trigger condition before listing outputs and exclusions. The parenthetical field list and make enumeration are dense but each item carries information; a slight trim would improve scannability.

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 an output schema handling return values and annotations covering safety, the description covers the remaining gaps: data scope, make coverage, and negative boundaries. It does not say what the response looks like when no sticker is on file for an otherwise valid VIN, which is the main residual ambiguity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only one parameter and schema coverage is 100%, so the schema already documents the VIN, including the note that I, O and Q never appear. The description reinforces the 17-character format but actually conflicts slightly with the schema's minLength 11 / maxLength 24, which could confuse an agent handling shorter non-standard identifiers.

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?

Uses a specific verb+resource ('check window sticker') and then enumerates exactly what is returned: vehicle identity fields, whether the original Monroney label is on file, recall count, and paint code location. It also scopes the tool to vehicles sold new in the US, so an agent knows the domain boundary without opening the 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?

Explicit trigger stated up front ('when the user has a 17-character VIN and wants to know what the vehicle is') and an explicit exclusion ('does not return accident, title or ownership history'). No sibling tools exist, so nothing more is needed in the way of alternatives.

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