DroneClear Thailand

Thailand drone check

drone_check

Read-onlyIdempotent

Use when someone asks whether or how they can fly a drone in Thailand, e.g. "can I fly my drone in Phuket", "do I need to register my DJI Mini in Thailand", "drone rules Bangkok", "Drohne Thailand Registrierung", "darf ich in Thailand mit der Drohne fliegen", "Drohne mitnehmen Thailand", "drone Thaïlande enregistrement", "puis-je faire voler mon drone en Thaïlande". Returns what a hobby or tourist pilot needs (CAAT and NBTC registration, insurance, flight rules, restricted areas for the place) with public sources, and a link to the DroneClear service information page that fits (DroneClear can handle the registration for you). It gives no prices. It covers hobby, leisure and tourism flights only: if the flight is paid or commercial (filming for a client), set purpose=commercial; the answer then gives only a scope notice and a contact link. If the user has not said whether the flight is for hobby or paid work, ask them first (purpose=unsure returns that question). Thailand only: places in other countries get an out-of-scope answer.

Input Schema

Name	Required	Description
`purpose`	No	Why they fly. Use commercial for any paid work, filming for a client or business use; leisure_tourism for holiday and hobby flights; unsure only if the user has not said (the tool then asks them).
`language`	No	Answer language: en, de, fr (match the user; for any other language use en and translate the answer).
`location`	No	City or area in Thailand, e.g. "Bangkok", "Phuket".
`weight_g`	No	Take-off weight in grams, if known.
`has_camera`	No	Does the drone carry a camera?
`drone_model`	No	Drone model, e.g. "DJI Mini 4 Pro". Give this or weight_g.
`has_caat_registration`	No	True if the pilot already holds a CAAT registration and only needs NBTC.

Output Schema

Name	Required	Description
`scope`	Yes	hobby_check = full answer; commercial_contact_only = the check does not cover paid work, only the contact link is given; needs_input = a question for the user must be answered first (weight, or hobby vs paid work); out_of_scope = place outside Thailand or drone over 25 kg.
`service`	Yes
`info_url`	Yes	Page on droneclearthailand.com with more on the place or drone model.
`language`	No
`question`	No
`weight_g`	No
`area_notes`	Yes
`disclaimer`	Yes
`contact_url`	No
`requirements`	Yes
`scope_notice`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 26, 2026

changedInput schema / properties / language / description

Previous value: -"Answer language: en or de (match the user)."New value: +"Answer language: en, de, fr (match the user; for any other language use en and translate the answer)."

changedInput schema / properties / language / enum

Previous value: -[
-  "en",
-  "de"
-]New value: +[
+  "en",
+  "de",
+  "fr"
+]

Changed3 schema fields changedOct 26, 2026

changedInput schema / properties / language / description

Previous value: -"Answer language: en, de, fr, ja, ko (match the user; for any other language use en and translate the answer)."New value: +"Answer language: en or de (match the user)."

changedInput schema / properties / language / enum

Previous value: -[
-  "en",
-  "de",
-  "fr",
-  "ja",
-  "ko"
-]New value: +[
+  "en",
+  "de"
+]

removedInput schema / properties / user_language

Removed value: -{
-  "description": "Two-letter ISO 639-1 code of the language the user writes in (e.g. es, sv, it), even if it is not one of the answer languages. Used only to count languages; never personal data.",
-  "type": "string"
-}

Changed3 schema fields changedOct 26, 2026

changedInput schema / properties / language / description

Previous value: -"Answer language: en or de (match the user)."New value: +"Answer language: en, de, fr, ja, ko (match the user; for any other language use en and translate the answer)."

changedInput schema / properties / language / enum

Previous value: -[
-  "en",
-  "de"
-]New value: +[
+  "en",
+  "de",
+  "fr",
+  "ja",
+  "ko"
+]

addedInput schema / properties / user_language

Added value: +{
+  "description": "Two-letter ISO 639-1 code of the language the user writes in (e.g. es, sv, it), even if it is not one of the answer languages. Used only to count languages; never personal data.",
+  "type": "string"
+}

First observedOct 10, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the read-only/idempotent annotations, it discloses what the answer contains (CAAT/NBTC registration, insurance, flight rules, restricted areas, public sources), what it omits (no prices), how commercial requests are handled (scope notice plus contact link), and how unsure requests behave. This is rich behavioral context and is consistent with the annotations.

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 description is front-loaded with the core use case and scope. It is somewhat long because of the many multilingual example phrases, but those examples serve the multilingual matching purpose and the remaining sentences add operational rules.

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?

Given the output schema and annotations, the description supplies the remaining critical context: Thailand-only scope, hobby/tourism-only scope, commercial fallback behavior, ask-if-unsure behavior, and no-price limitation. Nothing essential for correct invocation appears missing.

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 description coverage is 100%, so all seven parameters are already documented. The description reinforces the purpose enum behavior and the ask-first rule, but it largely repeats the schema's purpose description rather than adding substantially new parameter semantics.

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 user intent and resource: whether or how someone can fly a drone in Thailand, with concrete example queries. It clearly distinguishes the covered hobby/tourist case from commercial use and out-of-scope countries, so an agent can recognize the right tool.

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 explicit when-to-use guidance with examples, says to ask first when hobby vs paid work is unclear, instructs setting purpose=commercial for paid work, and states that non-Thailand locations get an out-of-scope answer. These are clear usage and exclusion rules.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All DroneClear Thailand tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?