Skip to main content
Glama

Window Sticker

by org.windowsticker
OverviewDiscussionsAdmin

Get a window sticker by VIN

get_window_sticker
Read-only

Look up the original factory window sticker (Monroney label) for a 17-character VIN, with an NHTSA specification decode. Returns links, never the PDF itself: page is the result page to give a person, and pdf is the label when one exists. For Toyota, Lexus, Nissan and Infiniti it returns only labels we already hold. Free, no key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vinYes17-character VIN. VINs never contain I, O or Q.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
vinYes
vehicleYesNHTSA vPIC decode. Null when vPIC did not recognise the VIN.
warningYes
windowStickerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / windowSticker / properties / paint
      Added value: +{
+  "anyOf": [
+    {
+      "properties": {
+        "code": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "color": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Exterior color as printed on the label, with its paint code where the label carries one (Toyota; Hyundai and Genesis when paint is a priced option). Null when there is no label or it names no color."
+}
    • changedOutput schema / properties / windowSticker / required
      Previous value: -[
-  "supported",
-  "available",
-  "pdf",
-  "page",
-  "note"
-]New value: +[
+  "supported",
+  "available",
+  "pdf",
+  "page",
+  "note",
+  "paint"
+]
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations: it discloses that only links are returned (not the PDF), explains the meaning of the two fields (page vs pdf), names the makes with restricted coverage, and states it is free with no key. This is rich, non-obvious behavioral context.

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?

Two dense sentences, front-loaded with the core lookup, then the return contract (links not PDF, page vs pdf), then the make restriction and cost. No filler.

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?

For a one-parameter read-only lookup with an output schema and full schema coverage, the description covers purpose, return contract, and coverage caveats. It doesn't reference the sibling routing tools, which would make it fully complete for an agent choosing among the three.

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 vin parameter is already documented with the 17-character constraint and the I/O/Q exclusion. The description restates the 17-character requirement but adds no format or validation detail beyond the schema, so baseline 3 applies.

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?

States a specific verb (look up) and resource (original factory window sticker / Monroney label) tied to a 17-character VIN, and adds an NHTSA spec decode. The special-case coverage note for Toyota/Lexus/Nissan/Infiniti further sharpens what the tool returns, distinguishing it from siblings.

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

Usage Guidelines4/5

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

The Toyota/Lexus/Nissan/Infiniti caveat and the 'returns links, never the PDF' behavior give clear context about when this tool applies and what to expect. It doesn't explicitly route to the sibling tools (which_makes_are_covered, why_no_sticker), so it stops short of full when/when-not guidance.

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

All Window Sticker toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources