flights

Get Aircraft

get_aircraft

Read-onlyIdempotent

Look up ONE aircraft by ICAO24 transponder hex (e.g. "a4d97e"). Returns registry details — registration/tail number, manufacturer, type, and registered owner/operator — plus its LIVE position if it is currently transmitting. No key required. Use for "what is aircraft ", "who operates ", "where is now". If you only have a flight number/callsign, use get_flight_route instead.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`icao24`	Yes	ICAO24 transponder address — 6 hex characters, e.g. "a4d97e" (case-insensitive)

Output Schema

TableJSON Schema

Name	Required	Description
`icao24`	Yes	ICAO24 transponder address
`heading`	Yes	True track heading in degrees
`altitude`	Yes	Barometric altitude in meters
`callsign`	Yes	Aircraft callsign (trimmed)
`latitude`	Yes	Current latitude in degrees
`velocity`	Yes	Velocity in meters per second
`longitude`	Yes	Current longitude in degrees
`on_ground`	Yes	Whether aircraft is on ground
`origin_country`	Yes	Country of origin

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedJul 25, 2026

changedInput schema / properties / icao24 / description

Previous value: -"ICAO24 transponder address (6 hex characters, e.g. \"a0b1c2\")"New value: +"ICAO24 transponder address — 6 hex characters, e.g. \"a4d97e\" (case-insensitive)"

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "icao24": "a0b1c2"
+  },
+  {
+    "icao24": "4b1d0f"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "altitude": {
+      "description": "Barometric altitude in meters",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "callsign": {
+      "description": "Aircraft callsign (trimmed)",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "heading": {
+      "description": "True track heading in degrees",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "icao24": {
+      "description": "ICAO24 transponder address",
+      "type": "string"
+    },
+    "latitude": {
+      "description": "Current latitude in degrees",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "longitude": {
+      "description": "Current longitude in degrees",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "on_ground": {
+      "description": "Whether aircraft is on ground",
+      "type": "boolean"
+    },
+    "origin_country": {
+      "description": "Country of origin",
+      "type": "string"
+    },
+    "velocity": {
+      "description": "Velocity in meters per second",
+      "type": [
+        "number",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "icao24",
+    "callsign",
+    "origin_country",
+    "longitude",
+    "latitude",
+    "altitude",
+    "velocity",
+    "heading",
+    "on_ground"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedMay 13, 2026

removedInput schema / examples

Removed value: -[
-  {
-    "icao24": "3c675a"
-  },
-  {
-    "begin": 1696032000,
-    "end": 1696118400,
-    "icao24": "3c675b"
-  }
-]

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "begin": {
-      "description": "Start of time interval as ISO 8601 timestamp",
-      "type": "string"
-    },
-    "count": {
-      "description": "Number of flights for this aircraft",
-      "type": "number"
-    },
-    "end": {
-      "description": "End of time interval as ISO 8601 timestamp",
-      "type": "string"
-    },
-    "flights": {
-      "description": "Flights for the specified aircraft",
-      "items": {
-        "properties": {
-          "arrival_airport": {
-            "description": "Estimated arrival airport code",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "callsign": {
-            "description": "Aircraft callsign (trimmed)",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "departure_airport": {
-            "description": "Estimated departure airport code",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "first_seen": {
-            "description": "First sighting time as ISO 8601 timestamp",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "icao24": {
-            "description": "ICAO24 transponder address",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "last_seen": {
-            "description": "Last sighting time as ISO 8601 timestamp",
-            "type": [
-              "string",
-              "null"
-            ]
-          }
-        },
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "icao24": {
-      "description": "ICAO24 transponder address (lowercase)",
-      "type": "string"
-    }
-  },
-  "required": [
-    "icao24",
-    "begin",
-    "end",
-    "count",
-    "flights"
-  ],
-  "type": "object"
-}New value: +null

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "begin": {
+      "description": "Start of time interval as ISO 8601 timestamp",
+      "type": "string"
+    },
+    "count": {
+      "description": "Number of flights for this aircraft",
+      "type": "number"
+    },
+    "end": {
+      "description": "End of time interval as ISO 8601 timestamp",
+      "type": "string"
+    },
+    "flights": {
+      "description": "Flights for the specified aircraft",
+      "items": {
+        "properties": {
+          "arrival_airport": {
+            "description": "Estimated arrival airport code",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "callsign": {
+            "description": "Aircraft callsign (trimmed)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "departure_airport": {
+            "description": "Estimated departure airport code",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "first_seen": {
+            "description": "First sighting time as ISO 8601 timestamp",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "icao24": {
+            "description": "ICAO24 transponder address",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "last_seen": {
+            "description": "Last sighting time as ISO 8601 timestamp",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "icao24": {
+      "description": "ICAO24 transponder address (lowercase)",
+      "type": "string"
+    }
+  },
+  "required": [
+    "icao24",
+    "begin",
+    "end",
+    "count",
+    "flights"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "icao24": "3c675a"
+  },
+  {
+    "begin": 1696032000,
+    "end": 1696118400,
+    "icao24": "3c675b"
+  }
+]

First observedApr 14, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover safety (readOnlyHint, openWorldHint, idempotentHint, destructiveHint: false). The description adds meaningful behavioral context: 'No key required' discloses authentication needs, and 'plus its LIVE position if it is currently transmitting' clarifies conditional data availability. This goes beyond annotations without contradicting them.

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 compact and front-loaded: identification, return contents, auth requirement, usage examples, and alternative tool in just five short sentences. Every sentence earns its place with no redundancy or filler.

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 simple one-parameter tool with an output schema, the description fully covers purpose, parameter semantics, usage examples, authentication, and alternatives. The presence of an output schema means return values are already defined, so no additional explanation is needed. Complete and self-contained.

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 coverage is 100% for the single parameter, with format, case-insensitivity, and examples already given. The description reiterates the ICAO24 hex format but adds little beyond the schema, so the baseline of 3 is appropriate.

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 is highly specific: 'Look up ONE aircraft by ICAO24 transponder hex' clearly identifies the verb, resource, and scope. It distinguishes itself from siblings like get_flights_in_area by emphasizing single-aircraft lookup, and explicitly mentions a sibling alternative. It also enumerates return contents (registry details, live position), leaving no ambiguity.

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?

The description gives explicit when-to-use guidance: 'Use for "what is aircraft <hex>", "who operates <hex>", "where is <hex> now"'. It also provides a clear exclusion: 'If you only have a flight number/callsign, use get_flight_route instead.' This is exactly the kind of direct, actionable usage guidance expected.

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

All flights tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0

Disambiguation2/5

Several tools have heavily overlapping purposes: ask_pipeworx and ask_pipeworx_beta are explicitly identical, ask_pipeworx_grounded and deep_research blur the query/research boundary, and the polymarket_* family plus bet_research all target prediction-market analysis. An agent would frequently struggle to pick the correct tool among these near-duplicates.

Naming Consistency3/5

All names are snake_case, but the verb/noun style is inconsistent: get_* for flight lookups, ask_* for queries, noun-style names like entity_profile and bet_research, and the polymarket_* prefix group. Some subgroups are internally consistent, but there is no single predictable pattern across the set.

Tool Count2/5

36 tools is far too many for a server named 'flights' — only 5 tools actually relate to aviation, while the rest span prediction markets, SEC/FDA data, npm packages, memory, and feedback. Even viewed as a general data platform, the count is heavy and the scope is unfocused.

Completeness2/5

For a flights server, the surface is severely incomplete: no scheduled flight status, delays, cancellations, or airport schedules — only live ADS-B snapshots. For the broader data-research domain the tools imply, coverage is better but still scattered, with no coherent lifecycle and several one-off utilities that don't connect to the rest.

Get Aircraft

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources