Autoza UK

Ask about a listed car

ask_about_car

Read-only

Answer a buyer's specific questions about ONE car listed on Autoza — previous owners, service history, warranty, number of keys, previous use, and the core specification. Every answer comes from the dealer's own listing and says so: it is what the dealer states, not an independent inspection. A question the listing does not answer comes back as unknown, which does not mean no. Pass the listing URL or id returned by search_used_cars. If the car has sold or been withdrawn, the response is status no_longer_for_sale with no answers. When the selling dealer has opted in to showing MOT history, the response also carries mot_history: that car's official DVSA MOT test record.

Input Schema

TableJSON Schema

Name	Required	Description
`listing_id`	No	The listing id, if you have it instead of the URL.
`listing_url`	No	The autoza.co.uk/listing/... URL returned by search_used_cars.
`include_unanswered`	No	Default true. Keep the questions we cannot answer in the response so the buyer can be told what is unknown.

Output Schema

TableJSON Schema

Name	Required	Description
`car`	No
`url`	No
`_note`	No	Where the figures come from: Autoza, prices in GBP, distances in miles.
`error`	No
`reason`	No
`status`	Yes	for_sale, or no_longer_for_sale / not_found when it is not.
`coverage`	No
`vat_note`	No
`available`	Yes
`price_gbp`	No
`price_vat`	No
`questions`	No
`price_note`	No
`price_text`	No
`mot_history`	No
`what_this_is`	No
`mileage_miles`	No
`tell_the_user`	No
`price_gbp_with_vat`	No
`availability_caution`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "_note": {
+      "description": "Where the figures come from: Autoza, prices in GBP, distances in miles.",
+      "type": "string"
+    },
+    "availability_caution": {
+      "type": "string"
+    },
+    "available": {
+      "type": "boolean"
+    },
+    "car": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "coverage": {
+      "type": "string"
+    },
+    "error": {
+      "type": "string"
+    },
+    "mileage_miles": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "mot_history": {
+      "type": "object"
+    },
+    "price_gbp": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "price_gbp_with_vat": {
+      "type": "number"
+    },
+    "price_note": {
+      "type": "string"
+    },
+    "price_text": {
+      "type": "string"
+    },
+    "price_vat": {
+      "type": "string"
+    },
+    "questions": {
+      "items": {
+        "properties": {
+          "answer": {
+            "description": "Null when the advert does not say; ifUnknown then says what to do.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "ifUnknown": {
+            "type": "string"
+          },
+          "known": {
+            "type": "boolean"
+          },
+          "provenance": {
+            "description": "Where an answer comes from. Null when there is none.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "question": {
+            "type": "string"
+          },
+          "questionKey": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "reason": {
+      "type": "string"
+    },
+    "status": {
+      "description": "for_sale, or no_longer_for_sale / not_found when it is not.",
+      "type": "string"
+    },
+    "tell_the_user": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    },
+    "vat_note": {
+      "type": "string"
+    },
+    "what_this_is": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "available",
+    "status"
+  ],
+  "type": "object"
+}

AddedSep 22, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Goes well beyond the readOnly/non-destructive annotations: answers are dealer-stated rather than independently inspected, 'unknown' does not mean 'no', sold/withdrawn listings return status no_longer_for_sale with no answers, and mot_history only appears when the dealer has opted in. That is exactly the provenance and failure-mode context an agent needs.

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?

Five dense sentences with no filler, ordered from what the tool answers, to provenance, to failure modes, to input sourcing, to conditional output. Nothing repeats the schema or annotations.

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?

An output schema exists, so return structure need not be explained, yet the description still pre-announces the meaningful response states (unknown, no_longer_for_sale, mot_history) that an agent must branch on. Nothing needed to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real sourcing guidance ('the listing URL or id returned by search_used_cars') and ties include_unanswered to the buyer-visible 'unknown' behavior, giving meaning beyond the field labels.

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 — answering a buyer's questions about ONE listed car — and enumerates the covered topics (previous owners, service history, warranty, keys, previous use, spec). The 'ONE car' scope cleanly separates it from search_used_cars, which returns listings.

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?

Explicitly routes the agent to feed it the listing URL or id returned by search_used_cars, and states the edge cases (unknown answer, no_longer_for_sale). It does not, however, distinguish itself from MOT-related siblings like check_mot_due_date or mot_outlook, so the agent must infer which is authoritative when a buyer asks about MOT.

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

All Autoza UK 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.

Resources

Need Help?