Sponsor Finder

Skilled Worker Salary Check

check_salary_threshold

Read-only

Check a UK job offer against the Skilled Worker visa salary thresholds and occupation going rates. Takes a job title (or SOC 2020 code), the annual salary, and the contracted weekly hours — hours matter, because going rates pro-rate. Returns a three-state verdict: eligible, not_eligible, or uncertain with the reason. Covers the standard Skilled Worker route only (not Health & Care or Global Business Mobility).

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": {
      "job_title": "<job_title>",
      "salary_gbp_per_year": "<salary_gbp_per_year>",
      "weekly_hours": "<weekly_hours>"
    },
    "name": "check_salary_threshold"
  }
}

Input Schema

Name	Required	Description
`phd_stem`	No	Applicant holds a PhD in a STEM subject relevant to the job.
`job_title`	Yes	The job title, e.g. "software developer" or "civil engineer". A 4-digit SOC 2020 code also works.
`new_entrant`	No	Applicant is a new entrant at the start of their career.
`phd_relevant`	No	Applicant holds a PhD in a subject relevant to the job.
`weekly_hours`	Yes	Contracted weekly hours. Required: going rates are published for a 37.5-hour week and pro-rate with actual hours, so the same salary can pass at 37.5 hours and fail at 45.
`salary_gbp_per_year`	Yes	Gross annual salary of the offer, in pounds. Decimals allowed.
`on_immigration_salary_list`	No	The job is on the Immigration Salary List (asserted by the user — the list itself is not modelled).

Schema Changelog

Changes observed during successful MCP inspections.

AddedAug 21, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations include readOnlyHint=true, and the description adds context about pro-rating going rates based on weekly hours, the three-state verdict, and the scope limitation. It doesn't contradict annotations and provides useful behavioral details beyond the read-only hint.

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 description is concise, front-loaded with the main purpose, and every sentence adds value. It covers the key inputs, the importance of hours, the output, and the scope limitation in a compact form.

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?

Given the tool's complexity (7 params, 3 required, no output schema), the description provides a clear overview of inputs, output, and scope. It doesn't detail return values, but the three-state verdict is mentioned. The schema covers parameter details, so the description is sufficient for an agent to select and invoke the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all parameters. The description adds value by explaining why weekly hours matter (pro-rating) and that the tool returns a verdict with reasons, which helps understand parameter usage. It doesn't repeat schema details but adds context.

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?

The description clearly states the tool checks a UK job offer against Skilled Worker visa salary thresholds and occupation going rates, taking specific inputs and returning a three-state verdict. It distinguishes itself from sibling tools (sponsor-related) by focusing on salary eligibility.

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

Usage Guidelines4/5

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

The description explains when to use it (checking a job offer against salary thresholds) and notes it covers only the standard Skilled Worker route, excluding Health & Care or Global Business Mobility. It doesn't explicitly mention alternatives, but the sibling tools are clearly different (sponsor checks), so the context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Sponsor Finder tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.