Skip to main content
Glama

Thai immigration office hours and address

thai_immigration_office
Read-onlyIdempotent

Use this when someone asks about a Thai immigration office: address, opening hours, whether it is open on Saturday, phone, which floor or counter, queue booking, what to bring for an extension, 90-day report, TM30 or re-entry permit. Covers Bangkok (Chaeng Watthana, Government Complex Building B), Jomtien (Pattaya, Chonburi), Chiang Mai, Phuket and Hua Hin (Prachuap Khiri Khan), and explains how to find the office for any other province. Examples: "Bangkok immigration office opening hours", "is Jomtien immigration open today", "Chiang Mai immigration address", "Phuket immigration queue", "where do I do my 90-day report in Hua Hin". Returns the office fields and registered facts with sources. Do not use for embassies or consulates abroad or for visa rules (thai_visa_details).

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": {
      "place": "<place>"
    },
    "name": "thai_immigration_office"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoOptional: what the user needs to do there.
placeYesTown, district or province, e.g. "Bangkok", "Pattaya", "Chiang Mai", "Phuket", "Hua Hin", "Chaeng Watthana".

Output Schema

NameRequiredDescriptionDefault
factsNo
notesNo
scopeYesanswered, compared, or needs_input (then ask the user "question" first).
fieldsNo
officeNo
summaryNo
page_urlNoGuide page on thailandstayplan.com (information only).
questionYes
office_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 readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds behavior beyond that: it says the answer includes office fields and 'registered facts with sources', and that it explains how to locate the office for provinces not in the covered list. It does not discuss data freshness, but the sourcing note partially compensates.

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?

Well front-loaded: trigger first, then coverage, examples, return behavior, and the exclusion last. The five example queries are somewhat repetitive filler, but they serve query-matching and the rest of the text is dense with distinct facts, so little is wasted.

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 read-only lookup tool with two parameters, full schema coverage, and an output schema, the description covers everything an agent needs: triggers, scope, exclusions, and a hint at return content. 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 adds meaning: it spells out the task intents (extension, 90-day report, TM30, re-entry) in prose and clarifies that 'place' can be any province via the 'how to find the office for any other province' behavior, not just the five enumerated cities. That is real value beyond the schema's example strings.

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 (Thai immigration office) and enumerates exactly the facts it returns: address, hours, Saturday opening, phone, floor/counter, queue booking, documents for extension, 90-day report, TM30, re-entry permit. It also states geographic scope (Bangkok Chaeng Watthana, Jomtien, Chiang Mai, Phuket, Hua Hin) and explicitly excludes embassies/consulates and visa rules, routing to thai_visa_details.

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 an explicit trigger ('Use this when someone asks about a Thai immigration office'), concrete example queries, and a hard exclusion ('Do not use for embassies or consulates abroad or for visa rules (thai_visa_details)'). An agent can route between this and the visa siblings without opening any schema.

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