sponsor-check
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SPONSOR_CHECK_HOME | No | Override the cache directory where the register is cached (default is ~/.cache/sponsor-check). The register is refreshed automatically when it is more than 24 hours old. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_sponsorA | Check whether a UK employer is licensed to sponsor visas on a given route. Args: company: Employer name as it appears in a job ad (legal or trading name). route: Visa route, e.g. "Skilled Worker" (default), "Global Business Mobility: Senior or Specialist Worker", "Scale-up", "Creative Worker". Returns a verdict (licensed, licensed_other_routes, possible_match, not_found), the matching register entries with their routes and A/B ratings, and caveats. |
| search_sponsorsB | Fuzzy-search the register and return the closest organisations, best first. |
| check_salaryA | Check a salary against the Skilled Worker salary requirement for an occupation. The requirement is the higher of a general threshold and the occupation's published going rate, so both the salary and the occupation code are needed. Args: salary: Gross annual salary offered, in pounds. soc_code: 4-digit SOC 2020 occupation code for the job, e.g. "2136". Ask the user or the employer for it; do not guess a code from the job title. new_entrant: True if the applicant qualifies for the new entrant rate, e.g. under 26, a recent UK student or graduate, in professional training, or in an eligible postdoctoral role. Returns a verdict (meets, below, occupation_ineligible, going_rate_unavailable, unknown_occupation), the required salary and the rule that produced it, the other discount options the job could qualify under, and the date the thresholds were published. |
| register_infoB | Dates and sources of the loaded data: the sponsor register and the salary thresholds. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
check_sponsor and search_sponsors both query the register and could be momentarily confused, but check_sponsor returns a verdict while search_sponsors returns ranked candidates, and the descriptions make this distinction clear. check_salary and register_info are clearly distinct.
check_sponsor, check_salary, and search_sponsors follow a verb_noun pattern, but register_info breaks it with a noun-only name and there's a minor plural inconsistency (sponsor vs sponsors). Still largely predictable and readable.
Four tools is a tight, well-scoped set for a focused sponsor/salary checking domain, with little redundancy. It sits slightly at the thin end but each tool earns its place.
The surface covers the key workflows: verifying a sponsor, fuzzy-discovering registered sponsors, validating salary against SOC codes, and checking data provenance. Minor gaps like route enumeration or bulk checking exist but core agent workflows are supported.