Skip to main content
Glama

Trip Desk: visa, travel advisories and trip briefs

Is it safe to go? US State Dept + UK FCDO travel advice for one country (live) ($0.040)

travel_advisory
Read-onlyIdempotent

Use for safety / duty-of-care screening of one destination: US advisory level 1-4 with summary, dates and link, UK FCDO alert status (advice against all / all-but-essential travel to all or parts), latest change, warnings and the entry-requirements excerpt, plus a combined headline. Optional: country. 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.

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_advisory"
  }
}

Input Schema

NameRequiredDescriptionDefault
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>.
countryNoDestination: ISO alpha-2/alpha-3 or English name. Default (bare call): TH

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 declare read-only, idempotent, non-destructive, open-world, but the description adds the material the agent actually needs beyond that: pricing ($0.040 per call), no API key or account, free with a Trip Desk Pass, payment rails (x402 over MCP with USDC on Base, MPP with USDC.e on Tempo), the fact that an unpaid call only returns payment terms and charges nothing, that bad input is rejected before charging, and that failed work is never charged. That is unusually rich billing and failure-mode disclosure for a paid tool.

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 payload description is front-loaded and every clause is substantive, including the endpoint equivalence (GET /v1/advisory). It is written as one dense run-on with a mid-sentence "Optional: country" fragment, so readability suffers slightly, but little is wasted.

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, no-output-schema tool, the definition covers inputs, the full return payload, payment mechanics, charging failure modes, and a data-source equivalence. There is no meaningful gap an agent would need filled before calling it correctly.

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 both parameters (pass token format and country formats including the TH default) are already documented. The description adds only that country is optional and repeats the default indirectly; it contributes no new format or constraint detail. Baseline 3 applies where the schema does the heavy lifting.

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 — safety / duty-of-care screening of one destination — and enumerates exactly what comes back: US advisory level 1-4 with summary, dates and link, UK FCDO alert status, latest change, warnings, entry-requirements excerpt, plus a combined headline. That is far more specific than any sibling (advisory_changes, visa_check) and lets an agent tell which one answers a safety question.

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 for safety / duty-of-care screening of one destination" gives a clear use context, and the one-country scoping is explicit with an optional country parameter and a stated default. It doesn't name an alternative or exclusion (e.g. when to prefer advisory_changes for change monitoring), so it stops short of full routing 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