Irish Used Car Market Data

What is this used car worth in Ireland?

price_check

Read-onlyIdempotent

Use to value a specific car: median, mean, quartiles and range of comparable Irish listings (same make, model, fuel, transmission if given, within 1 year and 30,000 km). Returns 404 (no charge) if there are fewer than 5 comparables. Use market_stats instead for a broad make/model overview, or analyze_listing when you already have a listing_id. Costs 0.005 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
`year`	Yes	Model year.
`model`	Yes	Vehicle model, case-insensitive.	Corolla
`fuel_type`	Yes	Fuel type, e.g. Petrol, Diesel, Electric, Petrol Hybrid, Petrol Plug-in Hybrid.	Diesel
`mileage_km`	Yes	Odometer reading in km.
`transmission`	No	Optional: Manual or Automatic.	Manual

Output Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes
`max_price_eur`	Yes
`min_price_eur`	Yes
`p25_price_eur`	Yes
`p75_price_eur`	Yes
`mean_price_eur`	Yes
`comparable_count`	Yes
`median_price_eur`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 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"
+]

addedInput schema / properties / transmission / enum

Added value: +[
+  "Manual",
+  "Automatic",
+  "manual",
+  "automatic"
+]

addedOutput schema / properties / query / required

Added value: +[
+  "make",
+  "model",
+  "year",
+  "mileage_km",
+  "fuel_type"
+]

addedOutput schema / required

Added value: +[
+  "query",
+  "comparable_count",
+  "median_price_eur",
+  "mean_price_eur",
+  "p25_price_eur",
+  "p75_price_eur",
+  "min_price_eur",
+  "max_price_eur"
+]

Changed28 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 / mileage_km / default
```
Added value: +60000
```
- addedInput schema / properties / mileage_km / example
```
Added value: +60000
```
- addedInput schema / properties / mileage_km / examples
```
Added value: +[
+  60000
+]
```
- addedInput schema / properties / model / default
```
Added value: +"Corolla"
```
- addedInput schema / properties / model / example
```
Added value: +"Corolla"
```
- addedInput schema / properties / model / examples
```
Added value: +[
+  "Corolla"
+]
```
- addedInput schema / properties / transmission / default
```
Added value: +"Manual"
```
- addedInput schema / properties / transmission / example
```
Added value: +"Manual"
```
- addedInput schema / properties / transmission / examples
```
Added value: +[
+  "Manual"
+]
```
- addedInput schema / properties / year / default
```
Added value: +2020
```
- addedInput schema / properties / year / example
```
Added value: +2020
```
- addedInput schema / properties / year / examples
```
Added value: +[
+  2020
+]
```
- addedOutput schema / properties / comparable_count / type
```
Added value: +"integer"
```
- addedOutput schema / properties / max_price_eur / type
```
Added value: +"number"
```
- addedOutput schema / properties / mean_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 / p25_price_eur / type
```
Added value: +"number"
```
- addedOutput schema / properties / p75_price_eur / type
```
Added value: +"number"
```
- addedOutput schema / properties / query / additionalProperties
```
Added value: +true
```
- addedOutput schema / properties / query / properties
```
Added value: +{
+  "fuel_type": {
+    "type": "string"
+  },
+  "make": {
+    "type": "string"
+  },
+  "mileage_km": {
+    "type": "integer"
+  },
+  "model": {
+    "type": "string"
+  },
+  "year": {
+    "type": "integer"
+  }
+}
```
- addedOutput schema / properties / query / type
```
Added value: +"object"
```
First observedOct 15, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already cover read-only/idempotent/openWorld, but the description adds material behavior the annotations cannot convey: the 404 + no-charge path when fewer than 5 comparables exist, the per-call price (0.005 USDC via x402), and that no-data results are free. Cost and failure semantics are precisely the things 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, then output shape, failure behavior, alternatives, and cost. No filler or restatement of the title; every clause carries operative information.

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 an output schema present, the description need not explain return values, and it correctly omits them while covering the gaps that matter: pricing, error/no-data behavior, comparable cohort definition, and sibling routing. 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.

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3, but the description goes further by explaining how inputs drive the match: same make/model/fuel, transmission 'if given' (confirming it is optional despite appearing in the properties list), and tolerance of within 1 year and 30,000 km. That matching-tolerance semantics is not derivable from the schema alone.

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 ('value a specific car') plus the exact output statistics (median, mean, quartiles, range) and the comparable-matching rule. It explicitly distinguishes itself from the sibling tools market_stats and analyze_listing by name, so an agent can route without opening any 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?

Gives explicit alternatives with selecting conditions: 'Use market_stats instead for a broad make/model overview, or analyze_listing when you already have a listing_id.' This is exactly when-to-use-this vs when-to-use-that guidance rather than implied context.

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?