Skip to main content
Glama

Check a UK employer on the register of licensed sponsors

abroad.check_uk_sponsor
Read-only

Use this when someone wants to check whether a UK employer named in a job offer holds a licence to sponsor workers from abroad, on the Home Office register of licensed sponsors as published on GOV.UK today. It returns the organisations whose name matches, with their town, rating and the routes they may sponsor, and what the rating means. Do not use it as proof that a job offer is real (a real employer's name can be used by someone else), for employers outside the UK, or to check a recruitment agency, which need not be on the register itself.

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": {
      "employer": "<employer>"
    },
    "name": "abroad.check_uk_sponsor"
  }
}

Input Schema

NameRequiredDescriptionDefault
townNoThe town or city the job is in, to narrow a common name.
employerYesThe employer's name as given in the offer, ideally its full registered name.

Output Schema

NameRequiredDescriptionDefault
townNo
foundYes
limitsYes
sourceYes
licenceYes
meaningYes
employerYes
explore_urlNo
more_matchesYes
register_dateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real behavioural context on top: the data source and freshness (register as published on GOV.UK today), the multi-match return shape (organisations, town, rating, sponsorable routes, and an explanation of the rating), and the important caveat that a name match does not prove an offer is genuine. It stops short of describing no-match or ambiguous-match behaviour, so not a full 5.

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?

Two sentences, front-loaded with the trigger condition followed by returns and exclusions; no filler. The second sentence is long and packs returns and caveats together, which slightly weakens scannability but every clause carries information.

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 two-parameter read-only lookup with an output schema and full annotation coverage, the description covers trigger, data provenance, return contents, and misuse cases. Nothing an agent needs in order to call it correctly is missing.

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% and both parameters carry their own descriptions, so the schema already does this work. The description references returned fields such as town and rating but adds no syntax, matching behaviour, or partial-name guidance beyond what the schema states. Baseline 3 applies.

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 and resource: checking whether a named UK employer holds a sponsor licence, against the Home Office register on GOV.UK. It also bounds the scope negatively (not proof of a real offer, not non-UK employers, not recruitment agencies), which lets an agent separate it from the sibling tools without opening any 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?

The opening clause gives an explicit trigger condition (someone wants to verify a UK employer named in a job offer), and the closing sentence gives three explicit when-not cases with the reason for each. Alternatives are not named by tool name, but the exclusion criteria are concrete enough to route an agent correctly.

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