Skip to main content
Glama

Get the original window sticker (API key)

get_original_sticker
Read-onlyIdempotent

Use this when the user wants the contents of the original factory window sticker (Monroney label) for a 17-character VIN: total MSRP, base price, destination charge, every factory option and package with its price, exterior and interior colour, engine, transmission, fuel economy, standard equipment, the factory paint code and a link to the original sticker PDF (valid 1 hour). Needs a StickerByVIN API key on a Starter plan or above, sent as "Authorization: Bearer sbv_live_..." or as ?api_key= on the MCP URL. Each call counts as one API call against the key’s monthly quota. Returns an error when no original sticker is on file for the VIN; check_window_sticker tells you that for free.

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

Input Schema

NameRequiredDescriptionDefault
vinYesThe 17-character Vehicle Identification Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial context beyond them: API key format and required plan tier, per-call quota consumption, one-hour expiry on the PDF link, and error behavior when no sticker is on file. These are exactly the operational facts an agent needs before spending a metered call.

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 trigger and packed with relevant detail with no filler sentences. It is a single dense run-on block, though, and would read better split into usage, auth, and cost sentences.

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?

For a one-parameter, metered, read-only lookup with no output schema, the description covers the return payload, authentication, cost, expiry, and failure mode. Nothing an agent needs in order to call it correctly 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?

With one parameter at 100% schema coverage, the schema already documents the VIN fully. The description reinforces that the VIN identifies the vehicle for the sticker but adds no format, normalization, or validation detail beyond the schema's own text.

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 and resource ('contents of the original factory window sticker (Monroney label) for a 17-character VIN') and enumerates the returned fields (MSRP, options, paint code, PDF link), so an agent knows exactly what it gets. It is clearly distinguishable from check_window_sticker, which is named as the cheaper existence check.

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?

Opens with an explicit trigger ('Use this when the user wants the contents of the original factory window sticker') and routes the alternative case explicitly: 'check_window_sticker tells you that for free.' Both the when and the when-not are stated with the condition that selects each.

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