Skip to main content
Glama

Tarve UK Sponsorship Jobs

Search the sponsor register

search_sponsors
Read-onlyIdempotent

Search licensed sponsors by name text, town, visa route and whether they have live jobs on Tarve. Returns the first page (20) with the total.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_sponsors"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoName text (optional).
townNoTown as on the register, e.g. "London" (optional).
routeNoVisa route, e.g. "Skilled Worker" (optional).
has_jobsNoOnly sponsors with live sponsored jobs on Tarve (optional).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context by stating the return shape: the first page of 20 plus a total. It does not cover ordering or how to retrieve subsequent pages.

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 filler, with the capabilities first and the result shape second. Nothing is redundant with the title or restated unnecessarily.

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 read-only, all-optional-filter search with no output schema, the description supplies the one thing an agent cannot infer: result size and total. Missing is any hint about pagination beyond page one or what fields a sponsor record contains, which matters more given there is no output schema.

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% and every parameter has its own description, so the description can only add marginal value. It does clarify that has_jobs means live jobs on Tarve specifically, which is slightly beyond the schema, but contributes nothing about matching semantics for q (prefix vs substring) or town normalization.

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?

States a specific verb (search) and resource (licensed sponsors) and enumerates the four filter dimensions. It does not name or differentiate itself from siblings like check_sponsor or register_changes, so an agent must infer that this is the multi-result lookup while check_sponsor is the single-record lookup.

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 word "Search"; there is no explicit when-to-use, no mention of when to prefer check_sponsor for a known name, and no note that all filters are optional and combinable. The agent can reasonably guess, but the definition leaves routing to inference.

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