Irish Used Car Market Data

Irish VRT and NOx levy estimate

estimate_irish_vrt

Read-onlyIdempotent

Use to estimate Vehicle Registration Tax and the NOx levy for a vehicle registered in Ireland, from its taxable value (OMSP), CO2 emissions and fuel type. Estimate only; verify against Revenue.ie. Use import_calculator instead for a full UK-to-Ireland landed-cost and margin estimate. Free (limited to 10 calls per day per IP).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`co2_g_km`	Yes	WLTP CO2 in g/km.
`fuel_type`	Yes	Fuel type, e.g. Petrol, Diesel, Electric, Petrol Hybrid, Petrol Plug-in Hybrid.	Diesel
`nox_mg_km`	No	NOx in mg/km. Default 40.
`price_eur`	Yes	Open market selling price (OMSP) in EUR.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`vrt_eur`	Yes
`total_eur`	Yes
`assumptions`	Yes
`nox_levy_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 / assumptions / required

Added value: +[
+  "omsp_eur",
+  "nox_mg_km",
+  "estimate_only"
+]

addedOutput schema / required

Added value: +[
+  "vrt_eur",
+  "nox_levy_eur",
+  "total_eur",
+  "assumptions"
+]

Changed18 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 / 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 / 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 / price_eur / default
```
Added value: +20000
```
- addedInput schema / properties / price_eur / example
```
Added value: +20000
```
- addedInput schema / properties / price_eur / examples
```
Added value: +[
+  20000
+]
```
- addedOutput schema / properties / assumptions / additionalProperties
```
Added value: +true
```
- addedOutput schema / properties / assumptions / properties
```
Added value: +{
+  "estimate_only": {
+    "type": "boolean"
+  },
+  "nox_mg_km": {
+    "type": "number"
+  },
+  "omsp_eur": {
+    "type": "number"
+  }
+}
```
- addedOutput schema / properties / assumptions / type
```
Added value: +"object"
```
- addedOutput schema / properties / nox_levy_eur / type
```
Added value: +"number"
```
- addedOutput schema / properties / total_eur / type
```
Added value: +"number"
```
- addedOutput schema / properties / vrt_eur / type
```
Added value: +"number"
```
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 declare readOnly/idempotent/non-destructive/non-open-world, so the safety profile is covered. The description still adds real value beyond them: a concrete rate limit (10 calls/day per IP), cost (free), and a reliability caveat pointing to Revenue.ie for verification. It stops short of describing calculation edge cases or precision, hence 4 rather than 5.

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 tight sentences with no waste: purpose first, caveat/alternative next, operational constraints last. The routing information is front-loaded where an agent will act on it.

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 read-only estimator with a full schema, an output schema, and complete annotations, the description supplies everything else an agent needs: what it computes, how accurate it claims to be, the sibling alternative, and the throttling limit.

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 every parameter is already documented (including the nox_mg_km default of 40, which the description never mentions). The description echoes OMSP/CO2/fuel type but adds no format, unit or default detail beyond the schema — baseline 3 is correct when the schema does the heavy lifting.

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 (estimate) and resource (Vehicle Registration Tax and NOx levy for an Irish-registered vehicle), plus the inputs it derives from (OMSP, CO2, fuel type). It explicitly names and contrasts itself with the sibling import_calculator, so an agent can route between them 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?

Gives both the use case ('Use to estimate...') and the exclusion, naming import_calculator as the right tool when a full UK-to-Ireland landed-cost and margin estimate is needed. It also adds an accuracy caveat ('Estimate only; verify against Revenue.ie') that sets expectations about authority of the result.

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?