Work Abroad Check

Where to report recruitment or visa fraud, or check an agency

abroad.where_to_report

Read-only

Use this when someone asks where to report a fake job or visa offer, a recruitment agency that took money, or trafficking, or how to check that a recruitment agency is licensed, in Ghana, Nigeria, Kenya, South Africa or Zimbabwe, or in the UK, Canada or the US. It returns the channels each government body publishes, with the source. Do not use it for other countries, and do not suggest that money will be recovered.

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

Input Schema

Name	Required	Description	Default
`country`	Yes	Where to report: where the person lives, or where the job is.

Output Schema

Name	Required	Description	Default
`limits`	Yes
`country`	Yes
`report_to`	Yes
`explore_url`	No
`sources_read_on`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint=false, so the safety profile is covered. The description adds that results are the channels each government body publishes with its source, plus the important constraint not to promise money recovery — useful context beyond the annotations. It stops short of describing response shape, though an output schema exists, so that gap is minor.

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?

One front-loaded sentence opens with the trigger and enumerates the scenarios, followed by a short exclusions clause — no filler. It is dense and long, which slightly taxes readability, but every clause carries information.

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?

For a single-required-parameter lookup with an output schema, the description covers scope, jurisdictions, and the key behavioural caveat, which is enough to invoke correctly. It could note whether multiple countries can be queried or how to respond when a country is unsupported, but nothing essential 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% with the single enum-backed country parameter fully described, so the baseline is 3. The description restates the jurisdiction list but adds no new syntax or disambiguation guidance (e.g. how to choose when the person lives in one country and the job is in another) beyond what the schema property description already says.

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 — reporting destinations for fake job/visa offers, agencies that took money, trafficking, and licence checks — and pins the exact set of countries covered. The scoping (reporting/verification, not offer assessment) makes it distinguishable from siblings like abroad.check_offer and abroad.check_uk_sponsor.

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?

Gives an explicit trigger ("Use this when someone asks where to report...") and explicit exclusions ("Do not use it for other countries, and do not suggest that money will be recovered"). Both the when and the when-not are stated, including a behavioural caution about not implying restitution.

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?