Skip to main content
Glama
Sign In

cars-data.com — Car Specs API

by com.cars-data
OverviewDiscussionsAdmin

List generations of a model

list_generations
Read-onlyIdempotent

Generations/facelifts of a model, with production years. This answers from a fixed 40-car demo set. Full catalogue: pay per request with x402, no key (GET /v1/variants/{id}/specs $0.05, /v1/search $0.005, /v1/variants $0.005, /v1/compare $0.1, USDC on Base); the Apify Actor, billed per event by Apify (https://apify.com/carsdatacom/car-specs-api); or the whole database as a licensed export (https://cars-data.com/en/api).

Input Schema

NameRequiredDescriptionDefault
localeNoResponse language, one of the 20 published languages (en, ro, fr, de, es, it, sr, hr, pt, pl, cs, sk, hu, no, sv, el, bg, da, ar, tr). Spec labels and enum values come back translated. Default: en.
model_idYesOpaque model id from a search_cars or filter_cars result, e.g. m_1a2b3c4d

Output Schema

NameRequiredDescriptionDefault
dataYesGenerations of the model

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / locale / description
      Added value: +"Response language, one of the 20 published languages (en, ro, fr, de, es, it, sr, hr, pt, pl, cs, sk, hu, no, sv, el, bg, da, ar, tr). Spec labels and enum values come back translated. Default: en."
    • changedInput schema / properties / model_id / description
      Previous value: -"opaque model id, e.g. m_1a2b3c4d"New value: +"Opaque model id from a search_cars or filter_cars result, e.g. m_1a2b3c4d"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "data": {
+      "description": "Generations of the model",
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "display_name": {
+            "description": "Generation / facelift name",
+            "type": "string"
+          },
+          "generation_id": {
+            "description": "Opaque generation id",
+            "type": "string"
+          },
+          "model_id": {
+            "description": "Opaque model id",
+            "type": "string"
+          },
+          "years": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Production years, e.g. '2019–2024'; '2021–' is still in production"
+          }
+        },
+        "required": [
+          "generation_id",
+          "model_id",
+          "display_name",
+          "years"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "data"
+  ],
+  "type": "object"
+}
  2. Changed5 schema fields changed
    • changedInput schema / properties / locale / enum
      Previous value: -[
-  "en",
-  "ro",
-  "fr",
-  "de",
-  "es",
-  "it",
-  "sr",
-  "hr",
-  "pt",
-  "pl",
-  "cs",
-  "sk",
-  "hu",
-  "no",
-  "sv",
-  "el",
-  "bg",
-  "da",
-  "ar"
-]New value: +[
+  "en",
+  "ro",
+  "fr",
+  "de",
+  "es",
+  "it",
+  "sr",
+  "hr",
+  "pt",
+  "pl",
+  "cs",
+  "sk",
+  "hu",
+  "no",
+  "sv",
+  "el",
+  "bg",
+  "da",
+  "ar",
+  "tr"
+]
    • addedInput schema / properties / model_id / description
      Added value: +"opaque model id, e.g. m_1a2b3c4d"
    • removedInput schema / properties / model_id / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / model_id / minimum
      Removed value: --9007199254740991
    • changedInput schema / properties / model_id / type
      Previous value: -"integer"New value: +"string"
  3. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), so the bar is lower; the description adds genuinely useful context by disclosing that results come from a fixed 40-car demo set rather than the full catalogue, and how the full data is obtainable. It doesn't discuss ordering or return shape, but the output schema handles that.

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 one crisp sentence, but the remainder is a dense pricing/ingestion catalogue with four endpoints and per-request prices, much of which reads as marketing rather than invocation guidance for this specific tool.

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 and 100% parameter coverage, the description only needs to convey scope and behavior; it does so by flagging the demo-set limitation. Minor gaps remain around ordering/pagination, but nothing essential for correct invocation 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?

Schema description coverage is 100% – model_id's opaque-id origin and locale's enum plus translation behavior are both fully documented in the schema. The description adds nothing about either parameter, so the baseline 3 applies.

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 first sentence gives a specific verb+resource: generations/facelifts of a model plus production years. It's clearly distinct from get_specs, get_images, and compare_variants by resource, though it never names a sibling to route the agent explicitly.

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?

The description implies when this is useful (you have a model and want its generation history) but gives no explicit when/when-not versus siblings like get_specs or filter_cars. The paid-alternative list is about scope and ingestion, not tool selection, so it only indirectly guides usage.

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

All cars-data.com — Car Specs API 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