Skip to main content
Glama

Carlytics VIN check

Check a car by VIN

check_vin
Read-onlyIdempotent

Check a used car by its 17-character VIN (vehicle identification number). Returns the car's make and model as decoded by Carlytics, plus a link to the free result page where the buyer can unlock the full vehicle history report (mileage records, inspection history, damage records where available, stolen-vehicle check, recalls, valuation). Use it whenever the user shares a VIN or asks whether a specific used car is OK to buy. Always show the user the report link.

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_vin"
  }
}

Input Schema

NameRequiredDescriptionDefault
vinYesThe 17-character VIN, as the user wrote it. Spaces and lowercase are fine.
languageNoThe user's language or market code for the result page, e.g. 'de' for German, 'pl' for Polish, 'us' for the United States. Omit if unsure.

Output Schema

NameRequiredDescriptionDefault
vinYes
makeYes
modelYes
reportUrlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedOutput schema / properties / year
      Removed value: -{
      -  "type": [
      -    "string",
      -    "null"
      -  ]
      -}
    • changedOutput schema / required
      Previous value: -[
      -  "vin",
      -  "make",
      -  "model",
      -  "year",
      -  "reportUrl"
      -]New value: +[
      +  "vin",
      +  "make",
      +  "model",
      +  "reportUrl"
      +]
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely useful context the annotations cannot: the free decode vs. paid unlock funnel, the fact that a report link is part of the result, and the operational rule 'Always show the user the report link' — which changes agent behavior downstream.

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?

Three sentences, front-loaded with the operation and return values, then the trigger, then the link instruction. The parenthetical enumeration of report contents is slightly long but earns its place by signaling the tool's value.

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?

An output schema exists, so return values needn't be spelled out, and the annotations cover the safety profile; the description still adds the report-link behavior and usage triggers. The one omission is what happens on an invalid or malformed VIN (error vs. partial decode), which would matter for a lookup keyed on a strict 17-character format.

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%: the vin parameter is documented with its 17-character format and the tolerance for spaces/lowercase, and the language enum is explained with examples and an 'Omit if unsure' default. The description adds only the length constraint already in the schema and never mentions the language parameter, 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 and resource ('Check a used car by its 17-character VIN') and immediately describes what comes back: decoded make/model plus a link to the free result page. It also enumerates what sits behind the link (mileage, inspections, damage, stolen check, recalls, valuation), so an agent knows exactly what capability this represents.

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?

Gives an explicit trigger: 'Use it whenever the user shares a VIN or asks whether a specific used car is OK to buy,' which covers the practical cases. There is no when-not-to-use guidance, but with no sibling tools there is no alternative to route against, so the gap is minor.

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