Skip to main content
Glama

UK Data for Agents

travel_advice_health

Read-onlyIdempotent

What jabs do I need, can I take my medication, and what is the ambulance number? Returns the FCDO 'Health' section for one country as headed plain-text subsections: emergency medical number, vaccine and health-risk pointers, medicines rules and local healthcare. Live from the GOV.UK Content API. The FCDO points to TravelHealthPro and NHS fitfortravel for vaccine detail, which this tool does not fetch; it is not medical advice. (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_health"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNostring, required, country name, alternative name (city, island) or GOV.UK slug, e.g. "ukraine"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the live GOV.UK Content API source, the returned format as headed plain-text subsections, the one-credit cost, and important limitations including that it is not medical advice and does not fetch vaccine detail. These are meaningful behavioral details not captured by readOnlyHint, idempotentHint, or openWorldHint.

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?

The description is front-loaded with the user-facing questions and then specifies the returned content, source, limitations, and cost. It is dense but mostly purposeful; the parenthetical cost note and disclaimer are useful, though the opening could be tightened slightly.

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 single-parameter, read-only tool with no output schema, the description gives enough context to invoke it correctly: it explains the country scope, the exact section returned, the response format, the source, and the key limitations. Nothing material 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 description coverage is 100%, so the country parameter's accepted forms and example are already documented in the schema. The description adds only that the tool applies to one country, which is consistent with the schema but does not add significant new parameter guidance.

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?

The description states a specific resource and verb: it returns the FCDO 'Health' section for one country. It also enumerates the returned subsections (emergency medical number, vaccines, medicines rules, local healthcare), which clearly distinguishes it from sibling travel advice tools such as safety or entry requirements.

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 opening questions establish the user need this tool addresses, and the description clearly bounds the tool by noting that vaccine detail is not fetched and pointing to TravelHealthPro and NHS fitfortravel instead. It does not explicitly route the agent to sibling tools like travel_advice_safety, but the health-specific scope is clear.

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