Irish Used Car Market Data

Irish market prices for a make and model

market_stats

Read-onlyIdempotent

Use for an overview of one model in the Irish used market: listing count, price range, median, and median price and mileage by model year and by fuel type. Use price_check instead to value one specific car with year, mileage, fuel type and optional transmission. Costs 0.01 USDC per call via x402; no-data results are free.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`make`	Yes	Vehicle make, case-insensitive.	Toyota
`model`	Yes	Vehicle model, case-insensitive.	Corolla

Output Schema

TableJSON Schema

Name	Required	Description	Default
`make`	Yes
`model`	Yes
`by_fuel`	Yes
`by_year`	Yes
`listing_count`	Yes
`max_price_eur`	Yes
`min_price_eur`	Yes
`median_price_eur`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 15, 2026

addedOutput schema / properties / by_fuel / items / required

Added value: +[
+  "fuel_type",
+  "count",
+  "median_price_eur"
+]

addedOutput schema / properties / by_year / items / required

Added value: +[
+  "year",
+  "count",
+  "median_price_eur",
+  "median_mileage_km"
+]

addedOutput schema / required

Added value: +[
+  "make",
+  "model",
+  "listing_count",
+  "median_price_eur",
+  "min_price_eur",
+  "max_price_eur",
+  "by_year",
+  "by_fuel"
+]

Changed16 schema fields changedOct 15, 2026

addedInput schema / properties / make / default
```
Added value: +"Toyota"
```
addedInput schema / properties / make / example
```
Added value: +"Toyota"
```
addedInput schema / properties / make / examples
```
Added value: +[
+  "Toyota"
+]
```
addedInput schema / properties / model / default
```
Added value: +"Corolla"
```
addedInput schema / properties / model / example
```
Added value: +"Corolla"
```
addedInput schema / properties / model / examples
```
Added value: +[
+  "Corolla"
+]
```

addedOutput schema / properties / by_fuel / items

Added value: +{
+  "additionalProperties": true,
+  "properties": {
+    "count": {
+      "type": "integer"
+    },
+    "fuel_type": {
+      "type": "string"
+    },
+    "median_price_eur": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / by_fuel / type
```
Added value: +"array"
```

addedOutput schema / properties / by_year / items

Added value: +{
+  "additionalProperties": true,
+  "properties": {
+    "count": {
+      "type": "integer"
+    },
+    "median_mileage_km": {
+      "type": "integer"
+    },
+    "median_price_eur": {
+      "type": "number"
+    },
+    "year": {
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / by_year / type
```
Added value: +"array"
```
addedOutput schema / properties / listing_count / type
```
Added value: +"integer"
```
addedOutput schema / properties / make / type
```
Added value: +"string"
```
addedOutput schema / properties / max_price_eur / type
```
Added value: +"number"
```
addedOutput schema / properties / median_price_eur / type
```
Added value: +"number"
```
addedOutput schema / properties / min_price_eur / type
```
Added value: +"number"
```
addedOutput schema / properties / model / type
```
Added value: +"string"
```

First observedOct 15, 2026

TDQS

A4.5/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, non-destructive, non-open-world). The description adds non-obvious operational context: each call costs 0.01 USDC via x402 and no-data results are free, which materially affects how an agent should budget and retry calls. It does not describe return format or pagination, but an output schema exists, so that omission is minor.

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 sentences, front-loaded with the use case, then the routing alternative, then the cost caveat. Every sentence carries decision-relevant information and nothing is repeated from 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?

With only two required string parameters, full schema coverage, an output schema covering return values, and annotations covering the safety profile, the description fills the remaining gaps — scope, sibling routing, and cost model. Nothing an agent needs to invoke this correctly 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% for both parameters (make, model, both case-insensitive with defaults and examples), so the schema carries the burden and the baseline is 3. The description's mention of model-year and fuel-type breakdowns describes output dimensions rather than the inputs, adding no extra meaning about how to supply make/model.

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?

The description states a specific verb and resource — a market overview for one model in the Irish used market — and enumerates exactly what is returned (listing count, price range, median, and breakdowns by model year and fuel type). It also explicitly names the sibling it is not, price_check, so an agent can distinguish the two without inspecting schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is stated explicitly: use this tool for a model-level overview, and use price_check instead when valuing one specific car with year, mileage, fuel type and optional transmission. Both the when and the when-not, along with the alternative, are present.

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

All Irish Used Car Market Data 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?