Skip to main content
Glama
noodlemctwoodle

uk-drone-airspace-mcp

by noodlemctwoodle
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Check drone rules

check_drone_rules
Read-only

See which UK open category drone rules apply to your consumer drone: subcategory, separation from people, Flyer/Operator IDs, and Remote ID. Provide a model or weight to get the answer.

Instructions

Which UK open category rules apply to a consumer drone: the subcategory (A1 fly over people, A2 near people, A3 far from people), the separation from uninvolved people, whether Flyer ID and Operator ID registration are needed, and when Remote ID is required. Give a model name from the catalogue (DJI, Autel, Potensic, HoverAir, Parrot) or a weight in grams plus any class mark. Rules follow the CAA class marks in force from 2026, including the EU C-class transition to the end of 2027.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoDate to assess the rules for; defaults to today. Use it to see what changes at a transition date.
modelNoDrone make and model, e.g. "DJI Mini 4 Pro", "Air 3S", "Mavic 3 Classic". Looked up in a curated catalogue of consumer drones.
formatNotext for a readable report (default), json for structured output, brief for two or three spoken-friendly sentences (use in voice conversations).text
weight_gNoTake-off weight in grams, when the model is not in the catalogue or a heavier battery is fitted.
class_markNoClass mark printed on the aircraft: an EU C-class (C0 to C4), a UK class (UK0 to UK4), or none for a legacy aircraft. Overrides the catalogue value.
has_cameraNoWhether the aircraft carries a camera. Defaults to the catalogue value, or true.
a2_certificateNoWhether the pilot holds an A2 Certificate of Competency (A2 CofC).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A4.1/5.0
Behavior4/5

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

With only readOnlyHint and openWorldHint annotations, the description adds valuable behavioral context: rules are assessed under CAA class marks in force from 2026, with the EU C-class transition noted through end of 2027, and it states what the check returns. It stops short of describing edge cases like an unrecognized model with no weight supplied.

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?

Three sentences, each with a distinct job: output summary, input invocation, and legal/date caveat. It is dense but not padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the essential decision-making context: what results to expect, how to identify the drone, and the legal regime/date sensitivity. It is slightly incomplete about behavior when conflicting or no identification inputs are provided, but the schema descriptions cover parameter-level details.

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 the baseline is 3. The description adds slight extra meaning by naming the catalogue brands and by instructing that a weight plus class mark can substitute for a model lookup, but it does not need to re-document the parameters.

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 the exact verb and resource: checking which UK open category rules apply to a consumer drone, and it enumerates the output categories (subcategory, separation, Flyer/Operator ID, Remote ID). This makes it distinct from the location, weather, preflight, and NOTAM sibling tools.

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?

The usage context is clear: it is for UK open category consumer drone rule questions, and no sibling tool overlaps with that function. It does not spell out exclusions such as non-UK or commercial operations, but the scenario is specific enough for an agent to route correctly.

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

Deploy Server

Other Tools