Skip to main content
Glama

Vehicle tax (VED) estimate

vehicle_tax_estimate
Read-onlyIdempotent

Estimated annual vehicle excise duty from CO2, engine size and first registration month, using the MotifyMe car tax logic.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "first_registered": "<first_registered>"
    },
    "name": "vehicle_tax_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
co2_gkmNoCO2 g/km
engine_ccNoengine size in cc
is_electricNotrue for fully electric
first_registeredYesYYYY-MM

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds a little behavior beyond that – the result is an estimate derived from a specific 'MotifyMe car tax logic' – but omits rate year applicability, currency, and how edge cases (pre-2001 registrations, missing CO2 for older cars) are handled.

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?

A single front-loaded sentence with no filler. It could earn a 5 only by also carrying routing or caveat information, which it does not.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter calculator with one required field and no output schema, the description never indicates what the response looks like (single figure, band breakdown) nor what happens when optional CO2 or engine size inputs are absent. Adequate but with real gaps for correct invocation.

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 coverage is 100%, so every parameter already has its own description; baseline 3 applies. The description restates the drivers (CO2, engine size, first registration month) but adds no rules about which combinations are required or how first_registered selects the applicable rate band.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Estimated annual vehicle excise duty') plus the inputs that drive it, so the tool is identifiable at a glance. It does not, however, distinguish itself from the sibling company_car_tax_calculator, which an agent could plausibly confuse with a VED/company-car-tax question.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the phrase 'annual vehicle excise duty' – the agent must infer this is for personal/vehicle VED rather than company car benefit-in-kind tax. There is no explicit when-to-use, when-not-to-use, or alternative named.

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.

Resources