UK government service fees, steps, processing times and recent changes, read from gov.uk.
Scored across 1 tool
There is only one tool, so there is no possibility of tool-selection ambiguity. The only routing decision is the `service` argument, which is well documented with aliases and a graceful nearest-key fallback for unknown values.
The single tool uses a clear snake_case verb_noun-style name (`uk_gov_process`) that matches common MCP conventions, so consistency is trivially satisfied. The verb 'process' is slightly vague for what is really a verified fact lookup, but the name is predictable and readable.
A one-tool surface is borderline thin even for a read-only reference server; all sixteen services and their metadata are funneled through a single call. It is a defensible design for a pure lookup service (no CRUD lifecycle is needed), but it leaves no room for a lighter listing/enumeration tool.
The tool returns rich, sourced facts (fees, processing times, eligibility, documents, change history) for sixteen major services, which covers the stated domain well. The notable gap is discoverability: the description explicitly says no query returns the service listing, so an agent cannot enumerate supported services or filter by change date.
Current UK government service facts verified against gov.uk, by service: passport-renewal-adult, passport-child, driving-licence-renewal, provisional-licence, change-address, vehicle-tax-sorn, register-to-vote, register-birth, register-death, blue-badge, self-assessment, national-insurance-number, universal-credit, eu-settlement-scheme, evisa, eta. Each service carries its official gov.uk page, the online startUrl, the page's last update date, figures (fee, processing time as stated, eligibility and required documents — each with value, unit, the quoted sentence and its source URL), and a dated list of changes since 2025 (passport fees from 8 April 2026, the ETA fee and enforcement, the BRP → eVisa switch, the end of the Universal Credit 2-child limit, Making Tax Digital for Income Tax). Common names resolve as aliases (passport → passport-renewal-adult, brp → evisa, sorn → vehicle-tax-sorn). No service returns the listing with the aliases; an unknown service answers covered:false with the nearest keys.
| Name | Required | Description | Default |
|---|---|---|---|
| service | No | one of: passport-renewal-adult, passport-child, driving-licence-renewal, provisional-licence, change-address, vehicle-tax-sorn, register-to-vote, register-birth, register-death, blue-badge, self-assessment, national-insurance-number, universal-credit, eu-settlement-scheme, evisa, eta, or an alias such as passport, brp, sorn, uc (omit to list all) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive and non-openWorld, so the safety profile is covered. The description adds genuinely new behavior: alias resolution (passport→passport-renewal-adult, brp→evisa, sorn→vehicle-tax-sorn) and the unknown-key response shape, which the annotations cannot convey.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loaded and organized by concern, but the 16-service enumeration duplicates the schema enum and the change-list examples (passport fees from 8 April 2026, BRP → eVisa switch, etc.) are verbose detail that an agent rarely needs at selection time.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description usefully describes the return payload (official page, startUrl, last update date, figures with value/unit/quoted sentence/source URL, dated change list). For a single-parameter read tool this is close to complete, though pagination/size limits are unaddressed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
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 largely restates the enum and the alias examples the schema already lists, though it does add the full alias mapping and the 'omit to list all' behavior — marginal value over structured data.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a precise verb+resource ('Current UK government service facts verified against gov.uk, by service') and enumerates the exact service keys covered, so an agent knows exactly what domain this answers for. No siblings exist to confuse it with.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives concrete routing behavior: omit the parameter to list all services, and an unknown service returns covered:false with the nearest keys. There is no sibling tool to contrast against, so full when/when-not guidance is not applicable, but the fallback semantics are made explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
uk_gov_processUK vehicle tax (VED) bands, expensive-car supplement, EV rules and MOT fees, sourced.
UK government data intelligence with proprietary scoring from 400+ sources
UK Integrated Online Tariff from HMRC's trade-tariff service: look up a UK commodity code, its…
UK tolls & charges: DVLA vehicle checks (ULEZ/CAZ/MOT/tax), prices, penalties, pay-by deadlines.
Add one secure layer between your agents and this server.