Skip to main content
Glama

Trip Desk: visa, travel advisories and trip briefs

Do I need a visa? passport -> up to 25 destinations (or the full map) ($0.020)

visa_check
Read-onlyIdempotent

Use when a traveller's nationality and destination(s) are known: visa-free / ETA / e-Visa / visa on arrival / visa required / no admission, max visa-free stay in days, what to do next and the official source. Omit destination for the passport's full map. Optional: passport, destination. PAID: $0.020 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/visa.

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

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>.
passportNoPassport country: ISO alpha-2/alpha-3 or English name. Default (bare call): US
destinationNoDestination country, or a comma-separated list of up to 25. Omit (with passport given) for the full map. Default (bare call): JP

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, covering the safety profile. The description adds genuinely useful behavior beyond that: $0.020 per call, payment via x402/MPP, unpaid calls return terms and charge nothing, invalid input is rejected pre-payment, and failed work is never charged. However, since the structured annotations already carry the core safety semantics, and the added content is mostly commercial rather than operational, this lands at a solid 3 rather than a 4 or 5.

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-loads the use condition and result shape, then the scoping rule, then payment. The payment-rail detail (x402 USDC on Base vs MPP USDC.e on Tempo) is dense but decision-relevant for a paid tool. Slightly long, but every sentence carries weight.

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 read-only, idempotent lookup with no output schema, the description names the returned fields, both defaults, the full-map mode, the paid-call and non-charging guarantees, and the pass option. An agent has everything needed to decide and invoke 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 coverage is 100%, so the schema already documents all three parameters including the US and JP defaults and the comma-separated destination list. The description only restates the 'omit destination for full map' behavior and the 25-destination cap, adding little beyond the structured fields. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: visa requirement lookup for a given passport and destination(s), and enumerates the exact result categories (visa-free / ETA / e-Visa / VOA / visa required / no admission), max stay, next steps, and official source. It also clarifies the 'omit destination' scope. It does not explicitly contrast with the sibling visa_peek, so it falls short of a 5.

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?

Gives a clear use condition (nationality and destination known) and an explicit variant (omit destination for the passport's full map). It does not name an alternative tool or state when not to use it, so the routing guidance is clear but not exhaustive.

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