Skip to main content
Glama

Tarve UK Sponsorship Jobs

Check a UK visa sponsor licence

check_sponsor
Read-onlyIdempotent

Is this organisation on the UK Home Office Register of Licensed Sponsors? Returns the best match (null when nothing resembles the name), its routes, rating, town, Companies House number, live sponsored jobs on Tarve, and up to 5 alternative matches.

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": {
      "name": "<name>"
    },
    "name": "check_sponsor"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe organisation's name as the person wrote it, e.g. "Revolut" or "Tesco Stores Limited".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds genuinely useful behavior: it performs fuzzy matching (null when nothing 'resembles the name') and caps alternatives at 5, which tells the agent how to interpret an empty or partial result.

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?

Two sentences, zero padding, and the core question is front-loaded before the return-shape enumeration. Every clause carries information an agent would otherwise have to guess.

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?

There is no output schema, so the description must carry the return contract — and it does, listing each returned field plus the null and alternative-matches cases. For a one-parameter, read-only lookup this is complete enough to call correctly and interpret the result.

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?

Only one parameter and schema coverage is 100%, so the baseline is already a 3. The description contributes one extra signal beyond the schema: because it returns the 'best match' and null on weak resemblance, the agent learns that a rough, human-written name is acceptable input rather than an exact legal string.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with the exact question the tool answers (is this organisation on the Home Office Register of Licensed Sponsors) and enumerates what comes back (routes, rating, town, Companies House number, live jobs, alternatives). The 'best match + up to 5 alternatives' framing implicitly distinguishes it from the sibling search_sponsors, but never names that sibling, so an agent must infer the split.

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

Usage Guidelines3/5

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

Usage is only implied by the framing: a single-organisation lookup rather than a broad search. There is no explicit when-to-use, when-not-to-use, or pointer to search_sponsors for exhaustive results, which is the obvious alternative among the siblings.

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