Skip to main content
Glama

cars-data.com — Car Specs API

by com.cars-data
OverviewDiscussionsAdmin

Search the full catalogue (paid)

search_catalogue
Read-only

Search all 103,372 variants (not only the 40-car demo). Returns opaque variant_ids for get_specs_full. Paid per call with x402 (USDC) — $0.005.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results, 1–50. Default: 10.
queryYesFree text matched against brand, model and variant names, accent- and punctuation-insensitive — e.g. 'bmw 3 series' or 'tesla model s'.
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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesMatches, most powerful first

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of results, 1–50. Default: 10."
    • 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 / query / description
      Previous value: -"e.g. 'bmw 3 series' or 'tesla model s'"New value: +"Free text matched against brand, model and variant names, accent- and punctuation-insensitive — e.g. 'bmw 3 series' or 'tesla model s'."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "data": {
+      "description": "Matches, most powerful first",
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "brand_slug": {
+            "type": "string"
+          },
+          "display_name": {
+            "description": "Full variant name, localized when a translation exists",
+            "type": "string"
+          },
+          "generation_id": {
+            "description": "Opaque generation id",
+            "type": "string"
+          },
+          "model_slug": {
+            "type": "string"
+          },
+          "variant_id": {
+            "description": "Opaque variant id, e.g. v_1a2b3c4d. Pass it to get_specs_full.",
+            "type": "string"
+          },
+          "year_from": {
+            "anyOf": [
+              {
+                "type": "number"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "First production year of the generation"
+          },
+          "year_to": {
+            "anyOf": [
+              {
+                "type": "number"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Last production year; 0 or null while still in production"
+          }
+        },
+        "required": [
+          "variant_id",
+          "display_name",
+          "brand_slug",
+          "model_slug",
+          "generation_id",
+          "year_from",
+          "year_to"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "data"
+  ],
+  "type": "object"
+}
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations cover safety (readOnlyHint, openWorldHint=false), but the description adds important context annotations cannot carry: the per-call cost, the x402/USDC payment mechanism, and the fact that returned variant_ids are opaque and must be resolved via get_specs_full. That cost disclosure is material for an agent deciding whether to call.

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?

Three short sentences, zero filler, and the differentiating scope plus the payment caveat are front-loaded. Every clause carries information an agent needs.

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 the description correctly supplies cost, scale, and the follow-up tool. It is nearly complete; the only gap is explicit routing guidance among the sibling search/filter tools.

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 query, limit, and locale are fully documented in the schema itself, including examples and the locale enum. The description adds no parameter-level meaning beyond that, 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?

States a specific verb and resource (search the catalogue) with a precise scope: all 103,372 variants rather than the 40-car demo. The scope distinction is useful, but no sibling is named, so the agent must infer that the 'demo' refers to search_cars and cannot tell how this differs from filter_cars.

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?

Implies when to prefer this tool (full coverage vs. the demo) and points forward to get_specs_full for resolving the returned IDs, which is genuinely helpful routing. However, it gives no explicit when-not guidance against search_cars or filter_cars, and no note that this call is paid while others may be free.

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