Skip to main content
Glama

Thai visa requirements, cost and rules

thai_visa_details
Read-onlyIdempotent

Use this when someone asks about ONE Thai visa, route or immigration topic: requirements, cost, fees, money test, documents, how and where to apply, processing time, insurance, whether they can work, family and dependants, extension or renewal. Examples: "how much is the Thailand Elite visa for 5 years", "Thailand Privilege card benefits", "DTV visa requirements", "digital nomad visa Thailand cost", "Thai retirement visa requirements", "non o visa Thailand", "O-A visa insurance", "LTR wealthy pensioner requirements", "Thailand golden visa", "marriage visa Thailand money", "education visa Thailand", "Thailand work permit cost", "permanent residence Thailand", "do I pay for the TDAC arrival card", "how does the Thai e-Visa work", "90-day report online". Routes and topics: exempt (30-day visa exemption), tr (tourist visa), dtv (DTV, digital nomad visa), nono (retirement visa: Non-O, O-A, O-X), marriage (Thai spouse or child), ltr (LTR 10-year visa), privilege (Thailand Privilege, formerly Thailand Elite), education (ED visa), work (Non-B and work permit), pr (permanent residence), tdac (arrival card), evisa (Thai e-Visa), reporting (90-day report, TM30, re-entry permit). Pass the route as the user names it and, if they ask about one aspect, the topic. Returns a short summary, key figures and the registered facts for that topic, each with source and date. Do not use to pick the best route for a person (use which_thai_visa), to compare routes (compare_thai_visas), for visa-free entry by passport (thai_entry_check), or for other countries. Not legal advice.

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": {
      "route": "<route>"
    },
    "name": "thai_visa_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
routeYesThe visa, route or topic as the user names it, e.g. "Thailand Elite visa", "DTV", "retirement visa", "Non-O", "LTR", "golden visa", "marriage visa", "TDAC", "90-day report".
topicNooverview (default), or the one aspect asked about: eligibility, money, fees, documents, where_to_apply, time, insurance, work (incl. tax facts), family, extension, watch.
nationalityNoOptional passport nationality, e.g. "American", "UK", "Australian": adds the page with missions, local-currency fees and national documents for that passport.

Output Schema

NameRequiredDescriptionDefault
factsNo
notesNo
routeNo
scopeYesanswered, compared, or needs_input (then ask the user "question" first).
topicNo
figuresNo
summaryNo
page_urlYesGuide page on thailandstayplan.com (information only).
questionYes
route_nameNo
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, destructiveHint=false and openWorldHint=false, so safety is covered. The description still adds real behavior: it returns a short summary plus key figures and registered facts each with source and date, and it flags 'not legal advice' and suggests passing the route as the user names it. Minor gap only in not mentioning output size or truncation.

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-loaded with the use-case, then examples, then the route glossary, then output and exclusions — a sensible order. The example query list and the route/topic glossary partially overlap, so a few lines could be trimmed, but none of it is filler for an agent that must map fuzzy user phrasings to a route key.

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 3-parameter read tool with an output schema and full annotations, everything an agent needs is present: trigger conditions, route vocabulary, topic enum intent, optional nationality behavior, output shape, and explicit exclusions.

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. The description nevertheless adds meaning: route accepts colloquial entity names (including the route glossary grouping non-O/O-A/O-X under 'nono'), topic should be set only when a single aspect is asked about, and nationality adds a passport-specific page with missions, local-currency fees and national documents.

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 names a specific resource (ONE Thai visa, route or immigration topic) and enumerates exactly what facts it returns (requirements, cost, money test, documents, processing time). It explicitly separates itself from siblings which_thai_visa, compare_thai_visas and thai_entry_check, so an agent can route without opening a schema.

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?

It gives both sides of the decision: use-when (single-route factual questions, with realistic example queries) and do-not-use-when (route selection, comparison, visa-free by passport, other countries), each naming the correct alternative tool.

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