Skip to main content
Glama

UK Immigration Lawyers — visa data tools

UK visa government fee estimate

visa_cost_estimate
Read-onlyIdempotent

Estimate the Home Office fees for a UK visa or citizenship application: application fee per applicant, Immigration Health Surcharge for the length of leave (adult and child rates, Home Office part-year rounding), priority or super-priority service, and route extras such as the citizenship ceremony. Routes: visitor, student, graduate, skilled3, skilled5, skilled3_in, skilled5_in, health, health5, fiance, spouse_ec, spouse_flr, ilr, nat, registration. Fee schedule 8 April 2026. Government fees only — no legal fees. Information, not advice.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
routeYesVisa route id. One of: visitor (Standard Visitor visa (6 months)); student (Student visa); graduate (Graduate visa); skilled3 (Skilled Worker visa — applying from outside the UK (up to 3 years)); skilled5 (Skilled Worker visa — applying from outside the UK (over 3 years)); skilled3_in (Skilled Worker — extension or switch inside the UK (up to 3 years)); skilled5_in (Skilled Worker — extension or switch inside the UK (over 3 years)); health (Health & Care Worker visa (up to 3 years)); health5 (Health & Care Worker visa (over 3 years)); fiance (Fiancé(e) visa (6 months)); spouse_ec (Spouse / Partner visa (entry clearance)); spouse_flr (Spouse / Partner extension — FLR(M)); ilr (Indefinite Leave to Remain (ILR)); nat (Naturalisation (British citizenship)); registration (Registration as British (child)).
priorityNoProcessing: none (standard), priority (~5 working days, £500 each), super (next working day, £1,000 each). Not available on citizenship routes; entry clearance offers priority only.
lengthMonthsNoLength of leave in months where the route offers a choice (e.g. Skilled Worker 12/24/36); the route's first published length when omitted or not offered.
adultDependantsNoAdult dependants (partner / 18+) applying with the main applicant. Ignored on routes where it does not apply (partner, citizenship).
childDependantsNoChild dependants under 18. For child registration this is simply the number of children.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / route / description
      Previous value: -"Visa route id. One of: visitor (Standard Visitor visa (6 months)); student (Student visa); graduate (Graduate visa); skilled3 (Skilled Worker visa (up to 3 years)); skilled5 (Skilled Worker visa (over 3 years)); health (Health & Care Worker visa); fiance (Fiancé(e) visa (6 months)); spouse_ec (Spouse / Partner visa (entry clearance)); spouse_flr (Spouse / Partner extension — FLR(M)); ilr (Indefinite Leave to Remain (ILR)); nat (Naturalisation (British citizenship)); registration (Registration as British (child))."New value: +"Visa route id. One of: visitor (Standard Visitor visa (6 months)); student (Student visa); graduate (Graduate visa); skilled3 (Skilled Worker visa — applying from outside the UK (up to 3 years)); skilled5 (Skilled Worker visa — applying from outside the UK (over 3 years)); skilled3_in (Skilled Worker — extension or switch inside the UK (up to 3 years)); skilled5_in (Skilled Worker — extension or switch inside the UK (over 3 years)); health (Health & Care Worker visa (up to 3 years)); health5 (Health & Care Worker visa (over 3 years)); fiance (Fiancé(e) visa (6 months)); spouse_ec (Spouse / Partner visa (entry clearance)); spouse_flr (Spouse / Partner extension — FLR(M)); ilr (Indefinite Leave to Remain (ILR)); nat (Naturalisation (British citizenship)); registration (Registration as British (child))."
    • changedInput schema / properties / route / enum
      Previous value: -[
      -  "visitor",
      -  "student",
      -  "graduate",
      -  "skilled3",
      -  "skilled5",
      -  "health",
      -  "fiance",
      -  "spouse_ec",
      -  "spouse_flr",
      -  "ilr",
      -  "nat",
      -  "registration"
      -]New value: +[
      +  "visitor",
      +  "student",
      +  "graduate",
      +  "skilled3",
      +  "skilled5",
      +  "skilled3_in",
      +  "skilled5_in",
      +  "health",
      +  "health5",
      +  "fiance",
      +  "spouse_ec",
      +  "spouse_flr",
      +  "ilr",
      +  "nat",
      +  "registration"
      +]
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint=false), so the description is free to add the non-obvious behavior: a pinned fee schedule (8 April 2026), Home Office part-year rounding on the IHS, adult vs child rates, and a clear disclaimer that output is information, not advice. That scoping and staleness disclosure is real value beyond the annotations; it stops short of describing the response shape.

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?

The purpose and pricing components are front-loaded in the first sentence, with the route enum, fee-schedule date, and exclusions following as scannable qualifiers. No filler sentences; the route list is arguably redundant with the schema but is compactly presented.

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

Completeness4/5

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

With a full-coverage schema and no output schema, the description carries the return-value burden and does so by enumerating the cost components an agent can expect. It omits currency of the returned figures (only implied by £ in the schema) and any indication of whether results are itemized or a single total, which are minor gaps for this complexity.

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% and both enums are exhaustively documented in the schema, so the baseline is 3. The description largely restates the route list already in the schema; its only additive parameter context is the note about Home Office part-year rounding for IHS length calculations.

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 (Home Office fees for a UK visa/citizenship application), then enumerates exactly what is priced: application fee, IHS, priority service, and route extras. The enum of supported routes and the sibling set (going_rate, right_to_work_assess) make the tool's scope unambiguous.

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 implied by "Estimate the Home Office fees..." and bounded by "Government fees only — no legal fees" plus "Information, not advice," which quietly rules out legal-cost or advice use cases. However, it never names an alternative tool or states the condition under which another sibling (e.g. going_rate) should be used instead, so the when-to-use guidance is implied rather than explicit.

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