Skip to main content
Glama

DroneClear Thailand

by com.droneclearthailand
OverviewDiscussionsAdmin

Server Details

Thailand drone rules for hobby pilots: CAAT/NBTC registration, insurance, flight limits. Sourced.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over 22 days
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL

TDQS

A3.9/5.0

Scored across 2 tools

Disambiguation4/5

drone_check answers regulatory/rules questions while how_droneclear_helps describes the commercial service offering; the boundary is spelled out in both descriptions. There is still some conceptual overlap since registration rules and registration service are often the same user question, but the routing intent is clear.

Naming Consistency3/5

Both names are snake_case, but the conventions differ: drone_check is noun_verb while how_droneclear_helps is a full phrase-style identifier. Readable and unambiguous, yet not a predictable pattern an agent could extrapolate to a third tool.

Tool Count3/5

Only two tools for a narrow, single-domain service (Thai drone rules plus service info), which is borderline thin. The two tools do earn their place, but a single well-structured tool with a mode parameter could plausibly have covered the same ground.

Completeness3/5

The core path—rules/registration questions and how DroneClear helps—is covered, including a scope notice and contact link for commercial flights. Gaps remain: no pricing or cost estimate surface, no way to check or start an actual registration, and commercial users hit a dead end beyond a contact link.

Available Tools

2 tools
drone_checkThailand drone checkA
Read-onlyIdempotent
Inspect

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.

NameRequiredDescriptionDefault
purposeNoWhy 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).
languageNoAnswer language: en, de, fr (match the user; for any other language use en and translate the answer).
locationNoCity or area in Thailand, e.g. "Bangkok", "Phuket".
weight_gNoTake-off weight in grams, if known.
has_cameraNoDoes the drone carry a camera?
drone_modelNoDrone model, e.g. "DJI Mini 4 Pro". Give this or weight_g.
has_caat_registrationNoTrue if the pilot already holds a CAAT registration and only needs NBTC.

Output Schema

NameRequiredDescription
scopeYeshobby_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.
serviceYes
info_urlYesPage on droneclearthailand.com with more on the place or drone model.
languageNo
questionNo
weight_gNo
area_notesYes
disclaimerYes
contact_urlNo
requirementsYes
scope_noticeNo

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.

how_droneclear_helpsHow DroneClear helpsA
Read-onlyIdempotent
Inspect

Use when someone asks whether DroneClear (or anyone) can handle drone registration or liability insurance for them in Thailand, e.g. "can someone register my drone in Thailand for me", "kann DroneClear meine Drohne in Thailand registrieren", "qui peut enregistrer mon drone en Thaïlande". Explains in a few lines how DroneClear Thailand helps hobby and tourist pilots (CAAT and NBTC registration handling, NBTC-only handling, liability insurance) with a link to the information page for each. It gives no prices. Not for paid or commercial flights.

NameRequiredDescriptionDefault
languageNoAnswer language: en, de, fr (match the user; for any other language use en and translate the answer).

Output Schema

NameRequiredDescription
info_urlYes
languageNo
servicesYes
disclaimerYes
scope_noticeNo

TDQS

A4/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, non-destructive, idempotent informational tool. The description adds useful behavioral context beyond the annotations: it explains that answers are brief, include links per topic, give no prices, and are not for commercial flights.

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 a clear 'Use when...' trigger and then adds relevant limits and scope. The three multilingual example queries add routing value, though they make the definition somewhat longer than strictly necessary.

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 low-complexity informational tool with one optional parameter, full schema coverage, annotations, and an output schema, the description gives everything needed to select and call it correctly. It covers purpose, triggers, limitations, and content scope.

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%, and the single optional 'language' parameter is fully documented in the schema, including fallback behavior. The description reinforces the multilingual nature through examples but does not add parameter meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states that this is an informational tool explaining how DroneClear helps with CAAT/NBTC registration and liability insurance in Thailand. It does not explicitly distinguish itself from the sibling tool drone_check, though its scope is narrow enough to infer the difference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives strong trigger guidance with 'Use when someone asks whether...' plus multilingual examples, and includes an explicit exclusion: 'Not for paid or commercial flights.' It does not name drone_check as an alternative for related drone compliance questions.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updates
    • Changeddrone_check2 fields changed
      • 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"
+]
    • Changedhow_droneclear_helps2 fields changed
      • 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"
+]
  2. 2 tool updates
    • Changeddrone_check3 fields changed
      • 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"
-}
    • Changedhow_droneclear_helps3 fields changed
      • 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"
-}
  3. 2 tool updates
    • Changeddrone_check3 fields changed
      • 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"
+}
    • Changedhow_droneclear_helps3 fields changed
      • 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"
+}
  4. 2 tool updates
    • First observeddrone_check
    • First observedhow_droneclear_helps

Related MCP Connectors

Related MCP Servers

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