Skip to main content
Glama
noodlemctwoodle

uk-drone-airspace-mcp

by noodlemctwoodle
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Check a take-off site

check_takeoff_site
Read-only

Assess any UK location for legal drone take-off by checking airspace restrictions, public rights of way, and landowner rules before flying.

Instructions

Assess a potential drone take-off spot in the UK. Returns the airspace verdict at the point, the nearest public rights of way (footpaths, bridleways, byways) with distances and the responsible council, and any known landowner rule (National Trust and Forestry England land, council byelaw or policy) at the point, plus open access land and SSSI or National Park designations as context. A public right of way is a strong indicator of legal access; rights-of-way data covers England and Wales only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latNoLatitude in decimal degrees (WGS84).
lonNoLongitude in decimal degrees (WGS84), negative west of Greenwich.
droneNoOptional drone make and model; adds the open category subcategory and the separation from people that applies to it.
placeNoPlace name, postcode or landmark in the UK, e.g. "Tyndale Monument", "BS1 6QF", "Durdle Door". Use lat/lon instead if you already have coordinates.
formatNotext for a readable report (default), json for structured output, brief for two or three spoken-friendly sentences (use in voice conversations).text
max_pathsNoMaximum rights of way to return.
a2_certificateNoWhether the pilot holds an A2 Certificate of Competency (A2 CofC).
search_radius_mNoSearch radius for rights of way in metres.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.3.0
    • addedInput schema / properties / a2_certificate
      Added value: +{
+  "default": false,
+  "description": "Whether the pilot holds an A2 Certificate of Competency (A2 CofC).",
+  "type": "boolean"
+}
    • addedInput schema / properties / drone
      Added value: +{
+  "description": "Optional drone make and model; adds the open category subcategory and the separation from people that applies to it.",
+  "maxLength": 80,
+  "minLength": 1,
+  "type": "string"
+}
    • changedInput schema / properties / format / description
      Previous value: -"text for a readable report (default), json for structured output."New value: +"text for a readable report (default), json for structured output, brief for two or three spoken-friendly sentences (use in voice conversations)."
    • changedInput schema / properties / format / enum
      Previous value: -[
-  "text",
-  "json"
-]New value: +[
+  "text",
+  "json",
+  "brief"
+]
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true and openWorldHint=true. The description goes beyond those by adding useful behavioral context: it discloses the geographic coverage limitation for rights-of-way data and the interpretive note that a public right of way is a strong indicator of legal access. No contradiction with annotations exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single dense paragraph with no filler. Every clause earns its place: the core action, the list of returned categories, and the crucial coverage caveat about England and Wales. It is front-loaded with the main purpose and keeps the most important interpretive guidance at the end.

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?

With no output schema, the description carries the burden of explaining return values, and it does so by listing all major result components: airspace verdict, public rights of way with distances, responsible council, landowner rules, open access land, and designations. It also covers a key limitation (data coverage) and a practical interpretation (RoW as legal access indicator). For a read-only assessment tool with 8 optional params, this is fully adequate.

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 parameters are already documented in the input schema (lat/lon bounds, place examples, format enum, max_paths, a2_certificate, search_radius_m). The description adds some context around the returned data but does not enrich parameter meaning beyond the schema, so the baseline 3 applies.

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 opens with a specific verb and object: 'Assess a potential drone take-off spot in the UK.' It then enumerates the concrete outputs (airspace verdict, rights of way, council, landowner rules, designations), making the tool's function unmistakable and clearly distinct from siblings like check_drone_rules or check_location.

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 description conveys clear context for use by explaining that a public right of way is a strong indicator of legal access and noting that rights-of-way data covers England and Wales only. It does not explicitly name sibling alternatives or state when to use another tool, but the scope and limitations are clear enough for an agent to decide when this tool applies.

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