Skip to main content
Glama

Trip Desk: visa, travel advisories and trip briefs

Trip readiness brief: visa + over-stay check + US/UK advisories + holidays + FX + checklist ($0.150)

trip_brief
Read-onlyIdempotent

Use before booking or confirming an international trip for a traveller: one call returns the visa rule for passport -> destination with an over-stay check against the dates, the US State Department level and UK FCDO alerts, public holidays inside the dates, the live exchange rate, Schengen specifics (90/180, EES, ETIAS status, passport-validity rule), a passport-validity check and a checklist with official links. Optional: passport, destination, depart, return (YYYY-MM-DD), home_currency, passport_expiry. PAID: $0.150 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/trip-brief.

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

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>.
departNoArrival date YYYY-MM-DD. Default: 30 days from today
returnNoDeparture date from the destination YYYY-MM-DD. Default: depart + 7 days
passportNoTraveller nationality: ISO alpha-2/alpha-3 or English name. Default (bare call): US
destinationNoDestination country. Default (bare call): JP
home_currencyNoISO 4217 code for the FX line. Default: the passport country's currency
passport_expiryNoOptional passport expiry date YYYY-MM-DD for the validity check

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 cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds substantial context beyond them: the $0.150 cost, x402/MPP payment paths, no API key needed, unpaid calls return payment terms and charge nothing, 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?

Front-loaded with the use case and the full return payload, then payment terms, then parameters. The payment paragraph is dense but each clause (price, auth, rails, unpaid behavior, no-charge guarantees) carries distinct information; only the restated $0.150 from the title is mild redundancy.

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?

With no output schema and seven optional parameters, the description must describe what comes back and how billing behaves — it does both, plus failure modes and an equivalent REST endpoint. An agent has everything needed to decide to call it and to anticipate the result shape and cost.

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 every parameter already carries its meaning and defaults. The description only restates the optional list with the YYYY-MM-DD format, adding no new semantics or inter-parameter constraints (e.g. that return must be after depart).

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 resource and enumerates exactly what one call returns: visa rule with over-stay check, US State Dept level and UK FCDO alerts, holidays, FX, Schengen specifics, passport-validity check and checklist. This makes it clearly distinguishable from narrower siblings like visa_check and travel_advisory.

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 before booking or confirming an international trip for a traveller" gives a clear triggering context, and the description positions it as the one-call aggregator superseding the single-purpose siblings. It stops short of explicitly naming visa_check or visa_peek as fallbacks for simpler needs.

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