Skip to main content
Glama

Trip Desk: visa, travel advisories and trip briefs

Visa category for one passport -> destination (free)

visa_peek
Read-onlyIdempotent

FREE preview: the visa category only (visa-free / ETA / e-Visa / on arrival / required / no admission) for one passport and one destination. visa_check adds stay length, official source and up to 25 destinations; trip_brief adds advisories, holidays, FX and a checklist.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "passport": "<passport>",
      "destination": "<destination>"
    },
    "name": "visa_peek"
  }
}

Input Schema

NameRequiredDescriptionDefault
passportYesPassport country (ISO code or English name)
destinationYesDestination country (ISO code or English name)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds two genuinely useful behavioral facts beyond the annotations: the call is free and the response is deliberately narrow, returning only the category. It does not describe error behavior for unrecognized countries or any rate/usage limits on the free tier.

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?

Two compact sentences with zero filler, and the key qualifier ('FREE preview ... only') is front-loaded so the agent immediately understands the tier and limits. The second sentence efficiently handles sibling differentiation in a single clause.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates well by enumerating the possible return values (visa-free / ETA / e-Visa / on arrival / required / no admission), which is exactly what an agent needs to interpret the response. Minor gap only: no guidance on invalid or ambiguous country inputs.

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% with both parameters described (ISO code or English name), so the schema carries the semantics. The description reinforces the cardinality constraint — one passport and one destination, not many — which is mildly useful but not much beyond the schema's string typing.

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 states a specific verb and resource (preview of the visa category) plus explicit scope: exactly one passport and one destination. It also names what it does not include (stay length, official source, multiple destinations), so an agent can distinguish it from visa_check and trip_brief without opening either schema.

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?

It clearly frames this as the free, quick-look tier and explains that visa_check adds stay length, official sources, and up to 25 destinations, while trip_brief adds advisories, holidays, FX, and a checklist — which routes the agent well. What's missing is a direct 'use visa_check instead if you need multiple destinations or sourcing' instruction rather than an implicit comparison.

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