DroneClear Thailand

How DroneClear helps

how_droneclear_helps

Read-onlyIdempotent

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.

Input Schema

Name	Required	Description	Default
`language`	No	Answer language: en, de, fr (match the user; for any other language use en and translate the answer).

Output Schema

Name	Required	Description	Default
`info_url`	Yes
`language`	No
`services`	Yes
`disclaimer`	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/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.

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?