Skip to main content
Glama

Do I need a visa for Thailand?

thai_entry_check
Read-onlyIdempotent

Use this when someone asks whether they need a visa to visit Thailand or how long they can stay visa-free with their passport: "do I need a visa for Thailand", "do US citizens need a visa for Thailand", "Thailand visa for UK citizens", "how long can Australians stay in Thailand without a visa", "is there still a 60-day visa exemption", "visa on arrival Thailand", "can I extend my visa exemption", "Thailand entry requirements 2026". Since 15 Sep 2026 passport holders of 60 countries get 30 days visa-free for tourism (the 60-day exemption ended), a few get 15 days or visa on arrival, bilateral agreements give 90, 30 or 14 days, and 21 countries lost visa-free entry. Returns the status for the passport, maximum days, the extension rule, the land-border limit, the free TDAC arrival card, and notes when the planned days or purpose need a visa, with sources. Do not use for long stays, retirement or work (which_thai_visa or thai_visa_details) or for other countries' entry rules.

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": {
      "nationality": "<nationality>"
    },
    "name": "thai_entry_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoOptional: planned days in Thailand on this trip.
purposeNoPurpose of the trip (default tourism). Visa-free entry is for tourism only.
nationalityYesThe passport as the user says it: country or adjective, e.g. "American", "UK", "German", "Brazil".

Output Schema

NameRequiredDescriptionDefault
factsNo
notesNo
scopeYesanswered, compared, or needs_input (then ask the user "question" first).
statusNo
countryNo
purposeNo
max_daysNo
page_urlNoGuide page on thailandstayplan.com (information only).
questionYes
rules_checkedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered; the description adds substantive policy context (60-day exemption ended on 15 Sep 2026, 21 countries lost visa-free entry) and discloses that the answer includes extension rules, land-border limits and TDAC. It partly restates return fields that the output schema already carries, and says nothing about citation recency beyond 'with sources'.

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?

The intent is front-loaded and the exclusion clause closes it cleanly, but the middle is a long run-on quote of eight sample queries followed by a dense policy sentence. The examples aid matching, yet a couple are redundant ('do I need a visa for Thailand' vs 'do US citizens need a visa for Thailand').

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 three-parameter, read-only lookup with a full output schema, everything the agent needs is present: trigger contexts, the policy baseline, what the result contains, and where to route out-of-scope questions. Nothing material is missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds real meaning: it explains that planned days and purpose are used to flag when a visa is actually required, and that visa-free entry is tourism-only. That tells the agent why supplying optional days/purpose changes the answer.

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 decision being answered (whether a passport needs a visa / how long visa-free) and the concrete policy basis (30 days from 15 Sep 2026, 15-day and VOA cases, bilateral 90/30/14). It explicitly distances itself from which_thai_visa and thai_visa_details, so an agent can separate it from siblings on the name alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a rich set of trigger phrasings for when to use it and explicit exclusions: no long stays, retirement or work (routed to which_thai_visa / thai_visa_details) and no other countries' entry rules. The when/when-not split is unambiguous.

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