Work Abroad Check

What a work or migration route abroad asks for

abroad.route_requirements

Read-only

Use this when someone asks what a route to work abroad needs: the UK Skilled Worker visa (sponsor, salary, English level, the costs paid to the government and the ones the employer must pay), the Health and Care Worker visa for doctors, nurses and health professionals, whether a UK care-worker visa is open to people abroad, the English test scores to join the UK nursing register, Canada's Federal Skilled Worker Program, or the US Diversity Visa ("green card lottery"). It returns the requirements as each government publishes them, each with its source and the date it was read. Do not use it for other routes or countries, to decide whether a particular person is eligible, or as legal advice: rules change, and the government's page decides.

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

Input Schema

Name	Required	Description	Default
`route`	Yes	One of: uk_skilled_worker, uk_health_and_care_worker, uk_care_worker, uk_nurse_registration, canada_federal_skilled_worker, us_diversity_visa.

Output Schema

Name	Required	Description	Default
`name`	Yes
`needs`	Yes
`notes`	Yes
`route`	Yes
`limits`	Yes
`country`	Yes
`explore_url`	No
`employer_pays`	No
`sources_read_on`	Yes
`you_pay_the_government`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.6/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 safety is covered. The description adds genuinely new context: results carry a source and a read date, and the data is time-sensitive by nature, which tells the agent to surface provenance and freshness. It stops short of describing pagination or coverage limits per route, 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?

Front-loaded with the trigger condition, then the covered routes, then the return contract and exclusions. The long enumeration sentence is dense but every listed route corresponds to a real enum value, so little is wasted; only slight trimming of parenthetical detail would tighten it.

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?

An output schema exists, so return shape needn't be explained, and the description still covers the essentials: scope, per-route subject matter, provenance/freshness, and explicit out-of-scope cases. For a single-parameter, read-only lookup tool this leaves no material gap an agent would need filled before calling it.

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 coverage is 100% and the single enum is fully documented, so the baseline would be 3. The description goes further by explaining what each enum value actually covers — sponsor, salary, English level and government vs employer costs for the Skilled Worker route, register test scores for nursing — which helps an agent pick the right value rather than matching labels.

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 ('returns the requirements as each government publishes them') and enumerates the exact six routes covered, so an agent knows the scope precisely. The closing exclusions ('other routes or countries', 'whether a particular person is eligible') also draw a clean line between this tool and the eligibility-checking siblings.

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?

Opens with an explicit trigger ('Use this when someone asks what a route to work abroad needs') and closes with three concrete when-not conditions: other routes/countries, personal eligibility decisions, and legal advice. The reason is given too ('rules change, and the government's page decides'), so the agent can route eligibility questions elsewhere without guessing.

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

All Work Abroad Check 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.

Resources

Need Help?