Skip to main content
Glama

New and recent Thai visa rules

thai_visa_rule_changes
Read-onlyIdempotent

Use this when someone asks what changed or what is new in Thai visa and immigration rules: "new Thailand visa rules 2026", "did the visa exemption change", "Thailand 30 day rule", "latest DTV changes", "retirement visa changes 2026", "Thailand Elite price change", "is the Thailand entry fee in force", "what changed since 2024". Returns dated changes, newest first, with in-force, announced, proposed or disputed status and sources. Optional filter by topic (a route or "entry") and by date. Do not use for the full rules of one route (thai_visa_details).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "thai_visa_rule_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNoOptional: only changes on or after this date, YYYY-MM-DD.
topicNoOptional: a route ("DTV", "retirement visa", "Thailand Elite", "LTR") or "entry" for visa exemption and arrival rules.
include_pendingNoInclude announced, proposed and disputed changes (default true).

Output Schema

NameRequiredDescriptionDefault
scopeYesanswered, compared, or needs_input (then ask the user "question" first).
sinceNo
topicNo
changesNo
page_urlNoGuide page on thailandstayplan.com (information only).
questionYes
rules_checkedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added value is the result shape: dated changes, newest first, each carrying in-force / announced / proposed / disputed status plus sources. That status vocabulary is genuinely useful for reasoning about authority of a change, though it stops short of saying how many items come back or how disputes are represented.

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 triggering condition, then behavior, then the alternative — a sound order. The quoted example queries take space but earn it by improving match recall; the sentence on topic/date filters is the only part that largely repeats the schema.

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?

An output schema exists and annotations carry the safety profile, so the description needs only trigger conditions, result semantics and routing — all present. An agent has everything required to select and call this tool correctly.

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 coverage is 100%, so all three parameters are already documented, including the topic/'entry' convention and the include_pending default. The description restates the topic and date filters without adding syntax or edge-case behavior (e.g., what an unrecognized topic does), so the baseline 3 applies.

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 resource (Thai visa and immigration rule changes) and scope (what changed / what is new), illustrated with concrete query phrasings. It explicitly names the sibling it is not (thai_visa_details), so an agent can discriminate without opening either 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?

Gives both sides: use when the question is about changes, novelty, or 'is X in force', with seven representative queries; and an explicit exclusion — not for the full rules of one route, which is routed to thai_visa_details. Nothing 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