Skip to main content
Glama

Trip Desk: visa, travel advisories and trip briefs

What changed? Travel advisory change feed, every country, US + UK, last N days ($0.040)

advisory_changes
Read-onlyIdempotent

Use daily for travel-risk monitoring: every US State Department advisory reissued/updated and every UK FCDO travel advice update in the window, newest first, with the current US level and each government's own change note, plus a per-country roll-up. One call replaces polling ~200 countries x 2 governments. Optional: days (1-30, default 7), countries (watch-list), source (both|us|uk), min_us_level (1-4). PAID: $0.040 per call, no API key or account, or free with a Trip Desk Pass. Pay with x402 over MCP (USDC on Base) or MPP over MCP (USDC.e on Tempo); an unpaid call returns the payment terms and charges nothing. Bad input is rejected before any payment; failed work is never charged. Same data as GET /v1/advisory/changes.

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

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window in days, 1-30. Default 7
passNoOptional Trip Desk Pass token (tp1....). With a valid pass this call is not charged. Prefer setting it once as the MCP header Authorization: Bearer <token>.
sourceNoWhich government(s): both (default), us or uk
countriesNoOptional watch-list: comma-separated ISO alpha-2/alpha-3 codes or English names (up to 50). Omit for every country
min_us_levelNoOnly US advisories at this level or higher (1-4); UK entries are then left out. Omit for all

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive, and open-world behavior, and the description goes well beyond that. It discloses result ordering, the paid model ($0.040/call, no API key, or free with a pass), both payment rails (x402/USDC on Base, MPP/USDC.e on Tempo), the fact that an unpaid call returns payment terms and charges nothing, and the safety guarantees that bad input is rejected before payment and failed work is never charged.

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 highest-value information (what changed, cadence, scope) before pricing and payment mechanics. It is dense but compact for the amount of decision-relevant content; the only mild redundancy is repeating the $0.040 price already present in the title.

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 carries the burden of describing returns, and it does: current US level, each government's own change note, per-country roll-up, newest-first ordering. Combined with full parameter coverage and explicit payment-terms behavior, an agent has everything needed to call this correctly and understand the cost path.

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 schema already documents every parameter including the pass token and the interaction where min_us_level excludes UK entries. The description restates days, countries, source, and min_us_level with their defaults and ranges but adds no syntax or format detail beyond the schema, so the baseline of 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?

The description names a specific resource and scope: every US State Department advisory reissued/updated plus every UK FCDO advice update in the window, newest first, with current US level, each government's change note, and a per-country roll-up. That is distinguishable at a glance from the sibling travel_advisory, which implies a point-in-time lookup rather than a change feed.

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?

"Use daily for travel-risk monitoring" gives an explicit cadence and context, and "One call replaces polling ~200 countries x 2 governments" frames the efficiency case for choosing it over repeated lookups. It does not explicitly say when to prefer a sibling (e.g. a single-country current advisory), so it stops short of full when-not guidance.

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