Skip to main content
Glama
Sign In

UK Data for Agents

by uk.co.reliness
OverviewDiscussionsAdmin

travel_advice_countries

Read-onlyIdempotent

Which countries and territories does the UK Foreign Office publish travel advice for, and what is the slug for each? Lists every FCDO travel advice destination with its GOV.UK slug and the alternative names GOV.UK maps to it (for example Dubai to United Arab Emirates, Tenerife to Spain), so other travel advice tools can be called with the right slug. Optional search narrows the list. Live from the GOV.UK Content API; it returns names only, not the advice itself. (cost: 1 credit)

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": "travel_advice_countries"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchNostring, optional, filter by country name, slug or alternative name such as a city or island (case-insensitive); default lists all

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent and non-destructive, and the description adds real context beyond them: the data is live from the GOV.UK Content API, the result is names/slugs only rather than advisory text, and the call costs 1 credit. The alternative-name aliasing behavior is a non-obvious trait disclosed up front.

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 core question, then scope, then usage rationale, then source and cost. The parenthetical examples and cost note are justified, though the sentence count is a little higher than strictly needed for a single-parameter lookup.

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?

For a one-parameter list tool with no output schema, the description covers what is returned (destination names, slugs, alternative names), the source and liveness of the data, and the absence of advisory content. Nothing an agent needs before calling it is missing.

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?

With one parameter at 100% schema coverage the baseline is 3, but the description adds meaning the schema only hints at: search matches alternative names such as cities and islands (Dubai, Tenerife) and that omitting it lists everything. That clarifies what the filter actually matches against, which is genuinely useful.

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 (lists every FCDO travel advice destination with its GOV.UK slug) and explicitly bounds scope with 'returns names only, not the advice itself', which separates it from siblings like travel_advice_country and travel_advice_safety. The alternative-name mapping purpose is also concrete, with worked examples (Dubai to United Arab Emirates, Tenerife to Spain).

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 gives a clear when-to-use: call this first to resolve a name into the slug that 'other travel advice tools can be called with'. It also rules out misuse by stating it does not return actual advice. It stops short of naming a specific sibling to use for the advice content itself, which keeps it from a 5.

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

All UK Data for Agents toolsInspect
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