Skip to main content
Glama

Get travel advice

get_travel_advice
Read-onlyIdempotent

Use this when the user asks about the official travel advice, safety warnings or entry requirements for one country, such as "is it safe to travel to Thailand?" or "what are the entry requirements for Japan?". Returns: the UK FCDO alert (which parts of the country it advises against travelling to) with its review date and latest change, and the US State Department level (1 to 4), summary and date, with official links. Input tips: pass one country name or two-letter ISO code; set section to entry-requirements, safety or health to add that part of the UK advice. If status is ambiguous, ask the user to pick one of candidates and call again with that name. If uk or us is none or unavailable, report the other side and its link; do not guess. Not for: visa rules for other passports (UK advice is for British citizens, US advice for US citizens), medical advice, or calling a country safe in your own words.

Input Schema

NameRequiredDescriptionDefault
countryYesCountry name in English or two-letter ISO code, such as "Thailand" or "TH". One country per call; use compare_advisories for several.
sectionNoWhat to include from the UK advice: summary (default, alert and dates only), entry-requirements, safety or health (adds that page's text). The US summary is always included.summary

Output Schema

NameRequiredDescriptionDefault
ukNo
usNo
queryYesThe country text as sent.
noticeYesThe limits of this information, to pass on.
statusYesok: see uk and us, each with its own status. not_found: no such country; check the spelling with the user. ambiguous: ask the user to pick one of candidates, then call again. unavailable: both sources are down; try again in a few minutes and give the official links. message says the next step.
countryNoThe country matched.
licenseYesAttribution for the UK text (Open Government Licence).
messageNoWhat to tell the user or do next when the answer is not a plain ok.
sectionNoThe section returned.
sourcesYesThe official sources, to link in the answer.
candidatesNoWith status ambiguous: the places the name could mean. Ask the user which one, then call again with that exact name.
citizenshipYesWho each government writes for. Tell the user this.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed43 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"Country name or two-letter ISO code, such as \"Thailand\" or \"TH\""New value: +"Country name in English or two-letter ISO code, such as \"Thailand\" or \"TH\". One country per call; use compare_advisories for several."
    • addedInput schema / properties / country / examples
      Added value: +[
      +  "Thailand",
      +  "TH",
      +  "Japan"
      +]
    • addedInput schema / properties / section / default
      Added value: +"summary"
    • changedInput schema / properties / section / description
      Previous value: -"What to include from the UK advice: summary (default), entry-requirements, safety or health. The US summary is always included."New value: +"What to include from the UK advice: summary (default, alert and dates only), entry-requirements, safety or health (adds that page's text). The US summary is always included."
    • addedOutput schema / properties / candidates / description
      Added value: +"With status ambiguous: the places the name could mean. Ask the user which one, then call again with that exact name."
    • addedOutput schema / properties / citizenship / description
      Added value: +"Who each government writes for. Tell the user this."
    • addedOutput schema / properties / country / description
      Added value: +"The country matched."
    • addedOutput schema / properties / license / description
      Added value: +"Attribution for the UK text (Open Government Licence)."
    • addedOutput schema / properties / message / description
      Added value: +"What to tell the user or do next when the answer is not a plain ok."
    • addedOutput schema / properties / notice / description
      Added value: +"The limits of this information, to pass on."
    • addedOutput schema / properties / query / description
      Added value: +"The country text as sent."
    • addedOutput schema / properties / section / description
      Added value: +"The section returned."
    • addedOutput schema / properties / section / enum
      Added value: +[
      +  "summary",
      +  "entry-requirements",
      +  "safety",
      +  "health"
      +]
    • addedOutput schema / properties / sources / description
      Added value: +"The official sources, to link in the answer."
    • addedOutput schema / properties / sources / items / properties / url / format
      Added value: +"uri"
    • addedOutput schema / properties / status / description
      Added value: +"ok: see uk and us, each with its own status. not_found: no such country; check the spelling with the user. ambiguous: ask the user to pick one of candidates, then call again. unavailable: both sources are down; try again in a few minutes and give the official links. message says the next step."
    • addedOutput schema / properties / uk / properties / alertStatus / description
      Added value: +"FCDO alert codes, such as avoid_all_but_essential_travel_to_parts. Empty when the FCDO advises against no travel."
    • addedOutput schema / properties / uk / properties / alertText / description
      Added value: +"One plain sentence for each alert code, to quote as written. Holds one sentence saying no travel is advised against when there is no alert."
    • addedOutput schema / properties / uk / properties / latestChange / description
      Added value: +"The FCDO's own note on what changed last."
    • addedOutput schema / properties / uk / properties / name / description
      Added value: +"Country name as GOV.UK writes it."
    • addedOutput schema / properties / uk / properties / reviewedAt / description
      Added value: +"When the FCDO last reviewed the advice, as an ISO 8601 time."
    • addedOutput schema / properties / uk / properties / reviewedAt / format
      Added value: +"date-time"
    • addedOutput schema / properties / uk / properties / section / description
      Added value: +"The asked-for part of the UK advice (when section is not summary)."
    • addedOutput schema / properties / uk / properties / section / properties / name / description
      Added value: +"Section name, such as Entry requirements."
    • addedOutput schema / properties / uk / properties / section / properties / text / description
      Added value: +"The section text as GOV.UK writes it."
    • addedOutput schema / properties / uk / properties / section / properties / truncated / description
      Added value: +"true when the text was cut; the full text is at url."
    • addedOutput schema / properties / uk / properties / status / description
      Added value: +"ok: advice found. none: this government publishes no advisory for the place. unavailable: its source could not be read; report the other government's advice and the official link, and do not guess this one."
    • addedOutput schema / properties / uk / properties / updatedAt / description
      Added value: +"When GOV.UK last published a change, as an ISO 8601 time."
    • addedOutput schema / properties / uk / properties / updatedAt / format
      Added value: +"date-time"
    • addedOutput schema / properties / uk / properties / url / description
      Added value: +"The GOV.UK travel advice page."
    • addedOutput schema / properties / uk / properties / url / format
      Added value: +"uri"
    • addedOutput schema / properties / us / properties / level / description
      Added value: +"US advisory level: 1 exercise normal precautions, 2 increased caution, 3 reconsider travel, 4 do not travel. null when the advisory names no level."
    • addedOutput schema / properties / us / properties / level / maximum
      Added value: +4
    • addedOutput schema / properties / us / properties / level / minimum
      Added value: +1
    • addedOutput schema / properties / us / properties / levelText / description
      Added value: +"The level as the State Department words it, such as \"Level 2: Exercise Increased Caution\"."
    • addedOutput schema / properties / us / properties / name / description
      Added value: +"Country name as the State Department writes it."
    • addedOutput schema / properties / us / properties / status / description
      Added value: +"ok: advice found. none: this government publishes no advisory for the place. unavailable: its source could not be read; report the other government's advice and the official link, and do not guess this one."
    • addedOutput schema / properties / us / properties / summary / description
      Added value: +"The advisory text as the State Department writes it."
    • addedOutput schema / properties / us / properties / summaryTruncated / description
      Added value: +"true when the summary was cut; the full text is at url."
    • addedOutput schema / properties / us / properties / updated / description
      Added value: +"When the State Department last updated the advisory, as an ISO 8601 time."
    • addedOutput schema / properties / us / properties / updated / format
      Added value: +"date-time"
    • addedOutput schema / properties / us / properties / url / description
      Added value: +"The US State Department advisory page."
    • addedOutput schema / properties / us / properties / url / format
      Added value: +"uri"
  2. Changed1 schema field changed
    • removedOutput schema / properties / note_from_openkrill
      Removed value: -{
      -  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
      -  "type": "string"
      -}
  3. Changed1 schema field changed
    • addedOutput schema / properties / note_from_openkrill
      Added value: +{
      +  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
      +  "type": "string"
      +}
  4. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly/idempotent/openWorld), and the description goes well beyond them by disclosing degradation behavior when one source is missing ('report the other side and its link; do not guess'), the disambiguation protocol, and source-scope caveats (UK advice for British citizens, US for US citizens). That is the kind of failure-mode guidance an agent cannot derive from structured fields.

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?

Front-loaded with the trigger, then explicitly partitioned into 'Returns:', 'Input tips:' and 'Not for:' segments. Every sentence carries non-redundant information; there is no filler despite the length.

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 two-parameter read-only lookup with a 100%-covered schema and an output schema, this description still covers everything the agent needs that structured data cannot express: trigger conditions, disambiguation, source-failure fallback, and scope exclusions.

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 both parameters are already thoroughly documented in the schema, including the enum values, the default, the ISO-code format, and the compare_advisories pointer. The description's 'Input tips' largely restate that, so the baseline 3 applies.

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+resource ('official travel advice, safety warnings or entry requirements for one country') with concrete user-utterance examples that pin down the trigger. The single-country scope is explicit, which is exactly what separates it from the sibling compare_advisories.

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 explicit when-to-use (user asks about one country's advice/safety/entry), how to handle ambiguity (ask user to pick a candidate, then call again), and a clear 'Not for:' exclusion list (other passports' visa rules, medical advice, paraphrasing safety verdicts). Nothing about routing is left 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.