Irish Used Car Market Data

UK-to-Ireland car import landed cost and margin

import_calculator

Read-onlyIdempotent

Use to judge a UK import: converts the GBP price and adds shipping, customs duty, import VAT, VRT, NOx levy and a cost buffer to give the landed cost in EUR. Provide make, model, year and mileage to also get the expected margin against the Irish market median. Duty and VAT default to 0 and must be set by the caller; results are estimates. Use estimate_irish_vrt instead when you only need VRT and NOx for an already Irish-valued vehicle. Costs 0.01 USDC per call via x402; no-data results are free.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`make`	No	Optional; with model, year and mileage_km enables the margin calculation.	Toyota
`year`	No	Optional model year.
`model`	No	Optional.	Corolla
`co2_g_km`	Yes	WLTP CO2 emissions in g/km (drives the VRT band).
`fuel_type`	Yes	Fuel type, e.g. Petrol, Diesel, Electric, Petrol Hybrid, Petrol Plug-in Hybrid.	Diesel
`nox_mg_km`	No	NOx mg/km for the NOx levy. Default 40.
`mileage_km`	No	Optional mileage in km.
`gbp_eur_rate`	No	GBP to EUR rate. Defaults to the service rate.
`shipping_eur`	No	Shipping/transport cost in EUR. Default 600.
`transmission`	No	Optional: Manual or Automatic.	Manual
`uk_price_gbp`	Yes	UK asking price in GBP.
`import_vat_pct`	No	Import VAT percent. Default 0; set 23 if it applies.
`other_costs_eur`	No	Other costs in EUR. Defaults to the service cost buffer (500).
`customs_duty_pct`	No	Customs duty percent. Default 0 (GB-built cars may attract ~10%).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`costs`	Yes
`gbp_eur_rate`	Yes
`estimate_only`	Yes
`is_arbitrage_deal`	Yes
`expected_margin_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 / costs / required

Added value: +[
+  "uk_price_eur",
+  "vrt_eur",
+  "nox_levy_eur",
+  "total_landed_cost_eur"
+]

addedOutput schema / required

Added value: +[
+  "gbp_eur_rate",
+  "costs",
+  "expected_margin_eur",
+  "is_arbitrage_deal",
+  "estimate_only"
+]

Changed49 schema fields changedOct 15, 2026
- addedInput schema / properties / co2_g_km / default
```
Added value: +125
```
- addedInput schema / properties / co2_g_km / example
```
Added value: +125
```
- addedInput schema / properties / co2_g_km / examples
```
Added value: +[
+  125
+]
```
- addedInput schema / properties / customs_duty_pct / default
```
Added value: +0
```
- addedInput schema / properties / customs_duty_pct / example
```
Added value: +0
```
- addedInput schema / properties / customs_duty_pct / examples
```
Added value: +[
+  0
+]
```
- 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 / gbp_eur_rate / default
```
Added value: +1.17
```
- addedInput schema / properties / gbp_eur_rate / example
```
Added value: +1.17
```
- addedInput schema / properties / gbp_eur_rate / examples
```
Added value: +[
+  1.17
+]
```
- addedInput schema / properties / import_vat_pct / default
```
Added value: +0
```
- addedInput schema / properties / import_vat_pct / example
```
Added value: +0
```
- addedInput schema / properties / import_vat_pct / examples
```
Added value: +[
+  0
+]
```
- 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 / nox_mg_km / default
```
Added value: +40
```
- addedInput schema / properties / nox_mg_km / example
```
Added value: +40
```
- addedInput schema / properties / nox_mg_km / examples
```
Added value: +[
+  40
+]
```
- addedInput schema / properties / other_costs_eur / default
```
Added value: +500
```
- addedInput schema / properties / other_costs_eur / example
```
Added value: +500
```
- addedInput schema / properties / other_costs_eur / examples
```
Added value: +[
+  500
+]
```
- addedInput schema / properties / shipping_eur / default
```
Added value: +600
```
- addedInput schema / properties / shipping_eur / example
```
Added value: +600
```
- addedInput schema / properties / shipping_eur / examples
```
Added value: +[
+  600
+]
```
- 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 / uk_price_gbp / default
```
Added value: +10000
```
- addedInput schema / properties / uk_price_gbp / example
```
Added value: +10000
```
- addedInput schema / properties / uk_price_gbp / examples
```
Added value: +[
+  10000
+]
```
- 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 / costs / additionalProperties
```
Added value: +true
```
- addedOutput schema / properties / costs / properties
```
Added value: +{
+  "nox_levy_eur": {
+    "type": "number"
+  },
+  "total_landed_cost_eur": {
+    "type": "number"
+  },
+  "uk_price_eur": {
+    "type": "number"
+  },
+  "vrt_eur": {
+    "type": "number"
+  }
+}
```
- addedOutput schema / properties / costs / type
```
Added value: +"object"
```
- addedOutput schema / properties / estimate_only / type
```
Added value: +"boolean"
```
- addedOutput schema / properties / expected_margin_eur / type
```
Added value: +"number"
```
- addedOutput schema / properties / gbp_eur_rate / type
```
Added value: +"number"
```
- addedOutput schema / properties / is_arbitrage_deal / type
```
Added value: +"boolean"
```
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 only declare it is a safe, idempotent, closed-world read; the description adds the non-obvious traits an agent needs: duty and import VAT silently default to 0 and must be set by the caller, outputs are estimates not quotes, the call costs 0.01 USDC via x402, and no-data results are free. That is real behavioral disclosure beyond the structured fields.

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 decision rule, then the output composition, then the alternative and cost caveat. No filler; the pricing sentence earns its place because it affects whether the agent calls at all.

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?

For a 14-parameter tool with an output schema and rich annotations, the description covers purpose, the cost breakdown, the estimate caveat, caller-set duty/VAT defaults, the pricing model, and the routing alternative. Nothing an agent needs to invoke it 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%, so the baseline is 3. The description restates the duty/VAT default pitfall that already appears in the schema, and its note that make/model/year/mileage unlock the margin calculation is also already in the parameter descriptions. It frames the inputs as a cost pipeline but adds little syntax or meaning the schema does not already supply.

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?

Specific verb+resource+output: it converts a GBP price and adds shipping, duty, import VAT, VRT, NOx levy and a buffer to produce a landed cost in EUR, plus an optional margin vs the Irish median. It also names the sibling it is not (estimate_irish_vrt). An agent can distinguish it from every listed sibling without opening a 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 trigger ("Use to judge a UK import"), an explicit condition for the secondary margin output (provide make, model, year, mileage), and an explicit alternative with the condition that selects it (estimate_irish_vrt for an already Irish-valued vehicle needing only VRT/NOx). Also states the pricing condition for calling at all.

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?