Skip to main content
Glama

Visa Requirements

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Visa Free Destinations

visa_free_destinations
Read-onlyIdempotent

Where can holders of a given passport travel without a visa? Lists every destination grouped by requirement: visa-free (with allowed stay days), visa on arrival, e-visa, eTA — plus counts for visa-required and no-admission. Optional filter to a single category. Answers "visa-free countries for X passport holders". Data: Passport Index snapshot (2026-02-18). Example: visa_free_destinations({ passport: "Germany" })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
passportYesPassport / nationality — ISO2, ISO3, or country name
requirementNoOptional: return only destinations in this category (default: full lists for visa_free, visa_on_arrival, e_visa, eta, plus counts for the rest)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "passport": "Germany"
+  },
+  {
+    "passport": "India",
+    "requirement": "visa_free"
+  }
+]
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint. Description adds behavioral details: grouping by requirement, including stay days for visa-free, counts for others, and data snapshot date (2026-02-18). No contradictions.

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 plus an example, front-loaded with purpose. Every sentence adds value; no redundancy. Structured with clear question-answer framing.

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?

No output schema, but description adequately explains output structure (grouped lists with stay days and counts). Data source and date are provided. Complete for a query tool of this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds meaning: explains default behavior (full lists for certain categories, counts for others), enumerates filter values, and provides an example. This adds value beyond schema.

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 clearly states the tool lists destinations by visa requirement for a given passport, with specific verb 'Lists' and resource 'destinations for a passport'. It distinguishes from sibling tools like visa_requirement (specific country) and visa_passport_compare (comparison).

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?

The description explains the tool's purpose and optional filter, implicitly guiding use for 'where can I go' queries. However, it lacks explicit when-not-to-use instructions or direct comparison to alternate tools, though sibling context provides differentiation.

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

All Visa Requirements toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources