cars-data.com — Car Specs API

Get full specs, any variant (paid)

get_specs_full

Read-only

Full localized specs for ANY variant in the catalogue, in 20 languages. Paid per call with x402 (USDC) — $0.05. Not charged when the id is unknown.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`locale`	No	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.
`variant_id`	Yes	Opaque variant id from search_catalogue, e.g. v_1a2b3c4d

Output Schema

TableJSON Schema

Name	Required	Description
`specs`	Yes	Every spec the variant carries, keyed by spec key (e.g. range_wltp_km)
`locale`	Yes	Language the response is in
`year_to`	Yes	Last production year; 0 or null while still in production
`power_hp`	Yes	Power, hp
`torque_nm`	Yes	Torque, Nm
`year_from`	Yes	First production year
`brand_slug`	Yes
`model_slug`	Yes
`variant_id`	Yes	Opaque variant id, e.g. v_1a2b3c4d. Pass it to get_specs / get_images / compare_variants.
`battery_kwh`	Yes	Traction battery capacity, kWh
`display_name`	Yes	Full variant name
`accel_0_100_s`	Yes	0–100 km/h, seconds
`price_new_eur`	Yes	New list price, EUR
`top_speed_kmh`	Yes	Top speed, km/h
`last_synced_at`	Yes	ISO-8601 time the data was last synced — surface it with the specs

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 14, 2026

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 / variant_id / description

Previous value: -"opaque variant id from search_catalogue, e.g. v_1a2b3c4d"New value: +"Opaque variant id from search_catalogue, e.g. v_1a2b3c4d"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "accel_0_100_s": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "0–100 km/h, seconds"
+    },
+    "battery_kwh": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Traction battery capacity, kWh"
+    },
+    "brand_slug": {
+      "type": "string"
+    },
+    "display_name": {
+      "description": "Full variant name",
+      "type": "string"
+    },
+    "last_synced_at": {
+      "description": "ISO-8601 time the data was last synced — surface it with the specs",
+      "type": "string"
+    },
+    "locale": {
+      "description": "Language the response is in",
+      "enum": [
+        "en",
+        "ro",
+        "fr",
+        "de",
+        "es",
+        "it",
+        "sr",
+        "hr",
+        "pt",
+        "pl",
+        "cs",
+        "sk",
+        "hu",
+        "no",
+        "sv",
+        "el",
+        "bg",
+        "da",
+        "ar",
+        "tr"
+      ],
+      "type": "string"
+    },
+    "model_slug": {
+      "type": "string"
+    },
+    "power_hp": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Power, hp"
+    },
+    "price_new_eur": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "New list price, EUR"
+    },
+    "specs": {
+      "additionalProperties": {
+        "additionalProperties": {},
+        "properties": {
+          "confidence": {
+            "anyOf": [
+              {
+                "type": "number"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Confidence score 0–1 for this value; null when not scored"
+          },
+          "label": {
+            "description": "Spec name in the requested language",
+            "type": "string"
+          },
+          "unit": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Unit of the value (km, kW, l/100km, …); null when unitless"
+          },
+          "value": {
+            "description": "The value: a string, number or boolean, already localized. Absent when the source holds no value"
+          }
+        },
+        "required": [
+          "label",
+          "unit",
+          "confidence"
+        ],
+        "type": "object"
+      },
+      "description": "Every spec the variant carries, keyed by spec key (e.g. range_wltp_km)",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "top_speed_kmh": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Top speed, km/h"
+    },
+    "torque_nm": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Torque, Nm"
+    },
+    "variant_id": {
+      "description": "Opaque variant id, e.g. v_1a2b3c4d. Pass it to get_specs / get_images / compare_variants.",
+      "type": "string"
+    },
+    "year_from": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "First production year"
+    },
+    "year_to": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Last production year; 0 or null while still in production"
+    }
+  },
+  "required": [
+    "variant_id",
+    "locale",
+    "display_name",
+    "brand_slug",
+    "model_slug",
+    "year_from",
+    "year_to",
+    "power_hp",
+    "battery_kwh",
+    "top_speed_kmh",
+    "torque_nm",
+    "accel_0_100_s",
+    "price_new_eur",
+    "last_synced_at",
+    "specs"
+  ],
+  "type": "object"
+}

AddedOct 11, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description earns credit by adding real behavioral context: paid per call via x402 in USDC at $0.05, and crucially that unknown variant ids are not charged. The auth/payment mechanism and failure-cost behavior are genuinely beyond the annotations.

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 tightly packed sentences with zero filler; the coverage scope, language count, cost, and billing exception are all front-loaded in order of importance.

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 need no explanation, and annotations cover the safety profile. The description supplies pricing and the no-charge-on-unknown-id rule, leaving only the comparison with the sibling get_specs unaddressed.

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%, so both parameters (variant_id origin, locale enum) are already fully documented in the schema, including the 20-language list. The description's '20 languages' restates schema content rather than adding format or defaulting detail, so 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?

States a specific verb and resource (get full localized specs for any catalogue variant) plus scope (20 languages), which an agent can act on directly. It does not explicitly distinguish itself from the sibling get_specs, so the 'full' vs. 'non-full' boundary is left to inference.

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 paid-per-call disclosure implies a cost tradeoff an agent should weigh, and 'ANY variant' hints at broader coverage than get_specs, but the description never states when to pick this over the free/cheaper sibling. Usage is implied rather than prescribed.

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 tools Inspect

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.