Irish Used Car Market Data

How fast a car model loses value in Ireland

depreciation

Read-onlyIdempotent

Use to estimate depreciation: median price by model year with year-on-year change, plus price change per 10,000 km. Needs at least 5 listings; otherwise returns 404 and you are not charged. Use market_stats instead for a simple market overview without depreciation calculations. 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
`fuel_type`	No	Optional: restrict to one fuel type.	Diesel

Output Schema

TableJSON Schema

Name	Required	Description	Default
`make`	Yes
`model`	Yes
`by_year`	Yes
`listing_count`	Yes
`price_change_per_10k_km_eur`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 15, 2026

addedInput schema / properties / fuel_type / enum

Added value: +[
+  "Petrol",
+  "Diesel",
+  "Electric",
+  "Petrol Hybrid",
+  "Diesel Hybrid",
+  "Petrol Plug-in Hybrid",
+  "Diesel Plug-in Hybrid",
+  "petrol",
+  "diesel",
+  "electric",
+  "petrol hybrid",
+  "diesel hybrid",
+  "petrol plug-in hybrid",
+  "diesel plug-in hybrid"
+]

addedOutput schema / properties / by_year / items / required

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

addedOutput schema / required

Added value: +[
+  "make",
+  "model",
+  "listing_count",
+  "price_change_per_10k_km_eur",
+  "by_year"
+]

Changed15 schema fields changedOct 15, 2026
- addedInput schema / properties / fuel_type / default
```
Added value: +"Diesel"
```
- addedInput schema / properties / fuel_type / example
```
Added value: +"Diesel"
```
- addedInput schema / properties / fuel_type / examples
```
Added value: +[
+  "Diesel"
+]
```
- 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_year / items
```
Added value: +{
+  "additionalProperties": true,
+  "properties": {
+    "change_vs_next_newer_year_pct": {
+      "type": "number"
+    },
+    "count": {
+      "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 / model / type
```
Added value: +"string"
```
- addedOutput schema / properties / price_change_per_10k_km_eur / type
```
Added value: +"number"
```
First observedOct 15, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds behavior they cannot express: the 5-listing minimum, the 404 failure mode, and the x402 cost model (0.01 USDC per call, no-data results free). That is exactly the operational context an agent needs before invoking a paid tool.

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?

Four compact sentences, front-loaded with purpose and scoping, then cost/error handling. Each sentence carries distinct load: scope, precondition, alternative, price. No filler or restatement of the title.

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 re-explained, yet the description still summarizes the key metrics. Combined with the documented error path and pricing, an agent has everything required to decide and call correctly.

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% – make, model, and fuel_type are each documented with defaults, examples, and an enum, so the schema carries the parameter burden. The description adds no format, casing, or defaulting guidance beyond what the schema supplies, so the baseline of 3 applies.

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+resource ('estimate depreciation') and immediately defines the computed outputs (median price by model year, year-on-year change, price change per 10,000 km). It also names a sibling it is not (market_stats) and the reason for the distinction, so an agent can route without opening either schema.

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?

Explicit when-to-use-not: 'Use market_stats instead for a simple market overview without depreciation calculations.' It also states the data precondition ('needs at least 5 listings; otherwise returns 404') and the commercial condition (charged vs free), leaving nothing to inference.

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?