Skip to main content
Glama

Xearno Tools

UK Road Tax Calculator (car tax / VED) — 2026-27 rates

uk_car_tax_ved
Read-only

What you’ll pay to tax your car this year — the first-year bill on a new one, the £200 everyone pays after that, and the £440 surcharge on pricier cars. Car tax arrives as two very different bills. The first year is a one-off charge set by the car’s CO2, running from a few hundred pounds to over £5,000 — which is why it usually disappears into the on-the-road price and is forgotten. Every year after that is a flat £200, and electric cars have paid it since 1 April 2025, the single fact a general-purpose AI is most likely to get wrong. Then there is the surcharge: any car listed above £40,000 pays an extra £440 a year from its second year to its sixth. For EVs that threshold rose to £50,000 on 1 April 2026 and was backdated to anything registered from April 2025, so even an answer that was correct last year has gone stale. Cars from 2001 to 2017 run on an older CO2 table, which is here as well.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
co2NoCO2 emissions (g/km) From the V5C logbook or the manufacturer. Sets the first-year rate for cars registered from April 2025 and the band for 2001–2017 cars. Ignored for EVs, and for the standard-year tax on post-2017 cars.
fuelNoFuel type Zero emission = pure electric (or hydrogen fuel-cell). Hybrids count as petrol/diesel — their £10 hybrid discount ended in April 2025. Non-RDE2 diesels pay one first-year band higher (see methodology; this tool assumes RDE2).petrolDiesel
regDateNoWhen was the car first registered? The decisive input — three different tax regimes by first-registration date (the date the car was first registered anywhere, not when you bought it). Cars first registered before 1 March 2001 are taxed by engine size instead and are out of scope here.new
listPriceNoManufacturer list price when new (£) The published list price on the day of first registration, including factory options and VAT — not what was actually paid. This decides the expensive-car supplement, and it sticks with the car for life.
yearOfOwnershipNoWhich year of the car’s life? Which year’s tax to show. The CO2-based first-year rate only exists for cars registered from April 2025 — for older cohorts "first year" is shown as a normal year. Years 2–6 are when the expensive-car supplement can apply.standard

TDQS

A4.9/5.0
Behavior5/5

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

The description discloses key behavioral traits beyond the readOnlyHint: it returns monetary amounts split into first-year and standard-year, and explains the surcharge logic for expensive cars. It highlights edge cases like the April 2026 EV threshold change and backdating to April 2025, warning that answers can become stale. It also notes the tool ignores CO2 for EVs and standard-year rates, and assumes RDE2 for diesels, providing transparency about calculation assumptions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the essential 'what you'll pay' summary and flows logically from first-year to standard-year to surcharge, then to older cars. It is longer than average, but each sentence carries unique information about rates, thresholds, or exceptions. Some redundancy exists (repeating dates like April 2025/2026), but the narrative structure helps readability. A minor trim could tighten it without losing value.

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 calculator with 5 parameters, 100% schema coverage, and no output schema, the description is extremely thorough. It covers first-year, standard-year, surcharge, EV rules, older cars, and out-of-scope pre-2001 cars. It also explains parameter interactions (e.g., co2 ignored for EVs, listPrice threshold changes). The description fully prepares an agent to select this tool and interpret inputs correctly across a wide range of scenarios.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

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

The description extensively adds meaning beyond the schema: it explains how 'co2' drives first-year rates for 2025+ cars and bands for 2001-2017 cars, how 'regDate' distinguishes three tax regimes, and how 'listPrice' triggers the expensive-car supplement. It also explains the significance of 'yearOfOwnership' (first vs standard vs after 6) and clarifies that EVs ignore co2. This compensates for the schema's defaults, giving agents the why behind each parameter.

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 clearly states the tool calculates UK car tax (VED) with 2026-27 rates, including first-year CO2-based rates, the standard £200 rate, and the expensive-car surcharge. It specifically mentions handling for different registration periods (2001-2017, post-2017) and EVs, distinguishing it from sibling tax tools by naming unique rates and rules. The verb 'what you'll pay' and resource 'road tax' are specific, with scope explicitly defined.

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?

The description explicitly explains when to use this tool: to find the annual and first-year tax for cars, with detailed rules for different registration dates and fuel types. It also states exclusions: cars registered before 1 March 2001 are out of scope because they're taxed by engine size. It clarifies that EVs are included and have been taxed since April 2025, and that the tool assumes RDE2-compliant diesels, guiding users on applicability.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Each tool targets a distinct niche (e.g., specific country tax rules, loan types, or legal calculations), with detailed descriptions that clarify boundaries. However, the large number of tools (66) could cause some confusion for an agent trying to select the right one for a general query, especially when multiple tools relate to the same country.

Naming Consistency4/5

Tool names follow a mostly predictable pattern: lowercase words separated by underscores, often starting with a country name (e.g., 'uk_stamp_duty_sdlt') or a topic (e.g., 'compound_growth'). There are minor deviations, such as abbreviations ('npv_irr', 'sip') and varying use of verbs, but overall the naming is clear and consistent.

Tool Count3/5

At 66 tools, the server is unusually large and covers an extensive range of financial and legal calculators. While each tool justifies its existence, the count exceeds the typical well-scoped range (3–15), making the server feel bloated. A more modular design might improve coherence.

Completeness4/5

The tool set covers a wide array of domains: personal income taxes, property taxes, loan calculations, investment returns, and specific country regulations. Minor gaps exist (e.g., missing tools for corporate taxes, general retirement planning, or insurance), but the overall coverage is thorough and addresses many niche scenarios that general AI handles poorly.

Resources