Skip to main content
Glama

check_visa_requirement

Check visa requirements between two countries. Returns visa type, stay duration, required documents, and application process for 39,585 passport-destination pairs in 15 languages.

Instructions

Check visa requirements between any two countries. Returns visa type (visa-free, e-visa, visa required, etc.), allowed stay duration, required documents, step-by-step application process, and travel tips. Covers 39,585 passport-destination pairs in 15 languages. Use this tool when the user asks about visa rules, entry requirements, travel documents, or whether they need a visa to visit a country. Requires an API key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
passportYesISO 3166-1 alpha-3 country code of the passport holder (e.g. 'FRA' for France, 'USA' for United States).
destinationYesISO 3166-1 alpha-3 country code of the destination country (e.g. 'JPN' for Japan, 'THA' for Thailand).
langNoLanguage code for the response. Supported: fr, en, es, pt, de, ja, ko, zh, ru, it, ar, hi, th, vi, tl. Defaults to 'en'.
Behavior3/5

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

No annotations provided. Description notes the tool requires an API key, which is helpful. But no mention of rate limits, error handling, or other behavioral traits.

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 sentences, front-loaded with purpose and deliverables, no wasted words.

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?

Description covers what the tool returns and when to use it. Lacks details on output format or error scenarios, but for a query tool, it is largely complete.

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 has 100% description coverage with clear descriptions of each parameter (country codes, language). Description adds no additional meaning beyond schema.

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?

Clearly states it checks visa requirements between two countries and lists return details. However, does not differentiate from the sibling tool 'quick_visa_check', which may serve a similar purpose.

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?

Explicitly tells when to use the tool (for visa rules, entry requirements). Does not mention when not to use or suggest alternative siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/MattJeff/orizn-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server