Skip to main content
Glama

flights

by io.github.pipeworx-io

Get Arrivals

get_arrivals
Read-onlyIdempotent

Aircraft currently ARRIVING at an airport — live ADS-B, no key required. Pass an ICAO code (e.g. "KSFO", "EGLL") and get inbound traffic descending toward the field, nearest first, with callsign, registration, aircraft type, altitude, descent rate and distance out. Use for "what is landing at right now", "inbound traffic to ". This is a live picture, not a scheduled timetable. (Historical windows via begin/end require OpenSky credentials and only work when self-hosting — OpenSky is unreachable from cloud egress.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNoOPTIONAL historical window end (Unix seconds, max 7 days after begin). Omit for live data.
beginNoOPTIONAL historical window start (Unix seconds). Requires OpenSky credentials and only works when self-hosting; omit for live data.
limitNoMax aircraft to return (1-200, default 50), nearest first.
airportYesICAO airport code, e.g. "KJFK", "EGLL", "KSFO" (4 letters, not the 3-letter IATA code)
radius_nmNoHow far out to look, nautical miles (1-250, default 40).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesNumber of arrival flights found
flightsYes

Schema Changelog

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

  1. Changed6 schema fields changed
    • changedInput schema / properties / airport / description
      Previous value: -"ICAO airport code, e.g. \"KJFK\", \"EGLL\" (not IATA \"JFK\")"New value: +"ICAO airport code, e.g. \"KJFK\", \"EGLL\", \"KSFO\" (4 letters, not the 3-letter IATA code)"
    • changedInput schema / properties / begin / description
      Previous value: -"Start of window, Unix timestamp in seconds"New value: +"OPTIONAL historical window start (Unix seconds). Requires OpenSky credentials and only works when self-hosting; omit for live data."
    • changedInput schema / properties / end / description
      Previous value: -"End of window, Unix timestamp in seconds (max 7 days after begin)"New value: +"OPTIONAL historical window end (Unix seconds, max 7 days after begin). Omit for live data."
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Max aircraft to return (1-200, default 50), nearest first.",
+  "type": "number"
+}
    • addedInput schema / properties / radius_nm
      Added value: +{
+  "description": "How far out to look, nautical miles (1-250, default 40).",
+  "type": "number"
+}
    • changedInput schema / required
      Previous value: -[
-  "airport",
-  "begin",
-  "end"
-]New value: +[
+  "airport"
+]
  2. Changed3 schema fields changed
    • changedInput schema / properties / airport / description
      Previous value: -"ICAO airport code (e.g. \"KLAX\", \"EGLL\")"New value: +"ICAO airport code, e.g. \"KJFK\", \"EGLL\" (not IATA \"JFK\")"
    • changedInput schema / properties / begin / description
      Previous value: -"Start of time range as Unix timestamp (seconds)"New value: +"Start of window, Unix timestamp in seconds"
    • changedInput schema / properties / end / description
      Previous value: -"End of time range as Unix timestamp (seconds, max 7 days after begin)"New value: +"End of window, Unix timestamp in seconds (max 7 days after begin)"
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of arrival flights found",
+      "type": "number"
+    },
+    "flights": {
+      "items": {
+        "properties": {
+          "arrival_airport": {
+            "description": "Estimated arrival airport ICAO code",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "callsign": {
+            "description": "Flight callsign (trimmed)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "departure_airport": {
+            "description": "Estimated departure airport ICAO code",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "first_seen": {
+            "description": "Unix timestamp of first radar contact",
+            "type": "number"
+          },
+          "icao24": {
+            "description": "ICAO24 transponder address",
+            "type": "string"
+          },
+          "last_seen": {
+            "description": "Unix timestamp of last radar contact",
+            "type": "number"
+          }
+        },
+        "required": [
+          "icao24",
+          "callsign",
+          "first_seen",
+          "last_seen",
+          "departure_airport",
+          "arrival_airport"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "count",
+    "flights"
+  ],
+  "type": "object"
+}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "airport": "KJFK",
+    "begin": 1609459200,
+    "end": 1609545600
+  },
+  {
+    "airport": "EGLL",
+    "begin": 1704067200,
+    "end": 1704153600
+  }
+]
  5. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare read-only and idempotent, but the description adds critical behavioral context: 'no key required', 'nearest first', the specific return fields, and the significant caveat that historical windows require OpenSky credentials and self-hosting ('OpenSky is unreachable from cloud egress'). This goes well beyond 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.

Conciseness5/5

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

The description is compact and front-loaded: the first sentence states the core purpose, the second provides usage and output details, and the third resolves ambiguity about live vs. scheduled data. The historical caveat is parenthetical to avoid distraction. Every sentence earns its place.

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 5 parameters, a detailed schema, rich annotations, and an output schema, the description is complete. It covers use cases, limitations, and technical requirements, leaving no significant gaps for an agent to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds meaning by giving ICAO examples, clarifying that results are 'nearest first', and explaining the begin/end historical limitation in context. It reinforces and extends the schema descriptions rather than merely repeating them.

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 clearly states the tool's purpose: 'Aircraft currently ARRIVING at an airport — live ADS-B' and specifies the output (inbound traffic with callsign, altitude, etc.). It distinguishes arrivals from siblings like get_departures and get_flights_in_area by focusing on inbound traffic to a specific airport.

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?

Explicit usage guidance is provided with example queries ('Use for "what is landing at <airport> right now"') and a clear disclaimer ('This is a live picture, not a scheduled timetable'). It also warns about historical window limitations. However, it does not explicitly name alternative tools, so it falls just short of a 5.

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

All flights toolsInspect
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.

Resources