Skip to main content
Glama

Compare Thai visas side by side

compare_thai_visas
Read-onlyIdempotent

Use this when someone compares two to four Thai visas or routes, or asks which is better or worth it: "Thailand Elite visa vs LTR", "LTR vs retirement visa", "DTV vs Thailand Elite", "DTV vs tourist visa", "Non-O vs O-A", "is the Thailand Privilege card worth it compared with a retirement visa", "cheapest way to stay in Thailand for 10 years", "retirement visa or Elite visa for a couple". Returns for each route: length, minimum age, money test, work rights, family, insurance, reporting, where to apply, and the government cost over the chosen number of years (fees and published Thailand Privilege prices; agent fees not included), with sources. Routes: 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). Do not use for a single route (thai_visa_details) or to rank all routes for a person (which_thai_visa). 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": {
      "routes": "<routes>"
    },
    "name": "compare_thai_visas"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageNoOptional age: flags routes with an age limit (retirement routes need 50 or over).
yearsNoYears of stay to cost (default 5).
routesYesTwo to four routes as the user names them, e.g. ["Thailand Elite", "LTR"] or ["DTV", "retirement visa"].

Output Schema

NameRequiredDescriptionDefault
scopeYesanswered, compared, or needs_input (then ask the user "question" first).
yearsNo
routesNo
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, destructiveHint=false and openWorldHint=false, so safety is covered without prose. The description nonetheless adds genuinely behavioral context the annotations cannot: cost figures come from government fees and published Thailand Privilege prices with agent fees excluded, sources are cited, and it carries a "not legal advice" caveat. It loses a point only because the per-route return field list largely restates what the output schema already conveys.

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 trigger condition before any supporting detail, and every block (when to use, what returns, route keys, when not to use) has a clear function. The long list of quoted example queries is slightly padded — a few would establish the same intent — but it is not wasteful enough to obscure the guidance.

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 comparison tool with an output schema, the description covers everything the agent needs beyond structured fields: selection conditions, exclusions with named alternatives, cost basis and its limits, and a legal disclaimer. No gap remains that would cause a misinvocation.

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 the baseline is 3, but the description earns an extra point by supplying the canonical route key vocabulary (exempt, tr, dtv, nono, marriage, ltr, privilege, education, work, pr, tdac, evisa, reporting) that the schema lacks as an enum, resolving how user-phrased routes map to accepted values. It also clarifies that cost is computed over the chosen number of years and that age triggers age-limit flags.

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 — comparing two to four Thai visa routes side by side — and enumerates exactly what is returned per route (length, age, money test, work rights, family, insurance, reporting, application location, government cost). It explicitly distinguishes itself from thai_visa_details (single route) and which_thai_visa (rank all routes), so an agent can route correctly 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?

When-to-use is given as a concrete set of trigger phrasings ("Thailand Elite visa vs LTR", "is the Thailand Privilege card worth it compared with a retirement visa"), and when-not-to-use is stated with the specific alternative tool for each excluded case. Nothing about selection is left to inference.

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