Skip to main content
Glama
Sign In

World Monitor

by app.worldmonitor
OverviewDiscussionsAdmin

Airport delays and airspace closures

get_aviation_status
Read-onlyIdempotent

Return the seeded airport disruption snapshot: one alert row per monitored airport (about 85 major airports worldwide) with iata, name, country and severity, built from AviationStack delay aggregates for international hubs, FAA ASWS delays for US airports and FAA NMS and ICAO NOTAM closures. Seeded about every 30 minutes and flagged stale after 90. The snapshot holds every monitored airport, so most rows are severity "normal" unless disrupted_only=true, and the default limit of 30 returns only part of it (0 for the whole list). Airport-level status only; no fares, schedules or flight tracks. Seeded-cache read with no live fetch: weight 1 on API plans, included in the signed-in free allowance. country is a case-insensitive name substring, iata selects one airport, limit caps the list (default 30, 0 for no cap).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_aviation_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
iataNoFilter to a single airport by IATA code (e.g. "JFK").
limitNoCap the alert list to at most this many items (default 30, pass 0 for no cap).
countryNoFilter to one country by name (case-insensitive substring, e.g. "united states").
summaryNoReturn counts + 3-item samples instead of full lists. Useful when you only need shape/size or want to budget context before drilling in.
jmespathNoOptional JMESPath projection applied to the response. See initialize.instructions for grammar and examples.
disrupted_onlyNoDrop airports with severity "normal" — keep only airports actually experiencing delays/closures. The bootstrap lists every monitored airport, so most rows are non-events without this.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / anyOf
      Added value: +[
+  {
+    "properties": {
+      "activationUnknown": {
+        "description": "Optional. True when an activation marker this tool consults could not be read, so `stale` was computed without knowing whether the producer has ever published. Distinguishes an unreadable marker from a producer that genuinely never ran — the same signal /api/health and /api/seed-health publish under this name.",
+        "type": "boolean"
+      },
+      "cached_at": {
+        "description": "ISO-8601 timestamp of the OLDEST contributing cache key, or null when no valid seed-meta is present.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "contentFreshnessPendingUntil": {
+        "description": "Optional ISO-8601 deadline while a cleanly absent content-freshness block is temporarily covered by deployment-order grace.",
+        "format": "date-time",
+        "type": "string"
+      },
+      "data": {
+        "properties": {
+          "delays-bootstrap": {
+            "properties": {
+              "alerts": {
+                "items": {
+                  "properties": {
+                    "country": {
+                      "type": "string"
+                    },
+                    "iata": {
+                      "type": "string"
+                    },
+                    "name": {
+                      "type": "string"
+                    },
+                    "severity": {
+                      "type": "string"
+                    }
+                  },
+                  "type": "object"
+                },
+                "type": "array"
+              }
+            },
+            "type": [
+              "object",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "freshnessUnknown": {
+        "description": "Optional. True when a freshness record could not be read (a cache timeout), so `stale` is true because freshness is unknown, not because the data was shown to be old. Retrying shortly will usually clear it.",
+        "type": "boolean"
+      },
+      "stale": {
+        "description": "True when any contributing cache key fails its freshness contract: fetched longer ago than its per-key maxStaleMin budget, below a declared minRecordCount, or — for keys that declare a content-age contract — carrying upstream observations older than maxContentAgeMin even though the fetch itself is recent. A recent cached_at with stale:true means the fetch is current but the underlying data has stopped advancing, so refetching will not help.",
+        "type": "boolean"
+      },
+      "unreadable": {
+        "description": "Optional. Labels of `data` sections whose cache read failed. Those sections are null because they could not be read, not because the dataset is empty. Retrying shortly will usually fill them.",
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "cached_at",
+      "stale",
+      "data"
+    ],
+    "type": "object"
+  },
+  {
+    "required": [
+      "projection"
+    ]
+  },
+  {
+    "required": [
+      "data",
+      "_attribution"
+    ]
+  },
+  {
+    "required": [
+      "_budget_exceeded"
+    ]
+  },
+  {
+    "required": [
+      "_jmespath_error"
+    ]
+  }
+]
    • removedOutput schema / properties
      Removed value: -{
-  "activationUnknown": {
-    "description": "Optional. True when an activation marker this tool consults could not be read, so `stale` was computed without knowing whether the producer has ever published. Distinguishes an unreadable marker from a producer that genuinely never ran — the same signal /api/health and /api/seed-health publish under this name.",
-    "type": "boolean"
-  },
-  "cached_at": {
-    "description": "ISO-8601 timestamp of the OLDEST contributing cache key, or null when no valid seed-meta is present.",
-    "type": [
-      "string",
-      "null"
-    ]
-  },
-  "contentFreshnessPendingUntil": {
-    "description": "Optional ISO-8601 deadline while a cleanly absent content-freshness block is temporarily covered by deployment-order grace.",
-    "format": "date-time",
-    "type": "string"
-  },
-  "data": {
-    "properties": {
-      "delays-bootstrap": {
-        "properties": {
-          "alerts": {
-            "items": {
-              "properties": {
-                "country": {
-                  "type": "string"
-                },
-                "iata": {
-                  "type": "string"
-                },
-                "name": {
-                  "type": "string"
-                },
-                "severity": {
-                  "type": "string"
-                }
-              },
-              "type": "object"
-            },
-            "type": "array"
-          }
-        },
-        "type": [
-          "object",
-          "null"
-        ]
-      }
-    },
-    "type": "object"
-  },
-  "stale": {
-    "description": "True when any contributing cache key fails its freshness contract: fetched longer ago than its per-key maxStaleMin budget, below a declared minRecordCount, or — for keys that declare a content-age contract — carrying upstream observations older than maxContentAgeMin even though the fetch itself is recent. A recent cached_at with stale:true means the fetch is current but the underlying data has stopped advancing, so refetching will not help.",
-    "type": "boolean"
-  }
-}
    • removedOutput schema / required
      Removed value: -[
-  "cached_at",
-  "stale",
-  "data"
-]
  2. Changed1 schema field changed
    • changedOutput schema / properties / stale / description
      Previous value: -"True when any contributing cache key is older than its per-key maxStaleMin freshness budget."New value: +"True when any contributing cache key fails its freshness contract: fetched longer ago than its per-key maxStaleMin budget, below a declared minRecordCount, or — for keys that declare a content-age contract — carrying upstream observations older than maxContentAgeMin even though the fetch itself is recent. A recent cached_at with stale:true means the fetch is current but the underlying data has stopped advancing, so refetching will not help."
  3. Changed1 schema field changed
    • addedOutput schema / properties / activationUnknown
      Added value: +{
+  "description": "Optional. True when an activation marker this tool consults could not be read, so `stale` was computed without knowing whether the producer has ever published. Distinguishes an unreadable marker from a producer that genuinely never ran — the same signal /api/health and /api/seed-health publish under this name.",
+  "type": "boolean"
+}
  4. Changed1 schema field changed
    • addedOutput schema / properties / contentFreshnessPendingUntil
      Added value: +{
+  "description": "Optional ISO-8601 deadline while a cleanly absent content-freshness block is temporarily covered by deployment-order grace.",
+  "format": "date-time",
+  "type": "string"
+}
  5. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new behavioral facts: data is seeded roughly every 30 minutes and flagged stale after 90, there is no live fetch, and the call costs weight 1 against API plans while being inside the free allowance. These are exactly the operational details an agent cannot get from structured fields.

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?

Front-loaded and information-dense, with the snapshot semantics and staleness stated first. The trailing sentence re-explains country, iata and limit already covered earlier in the paragraph, which is mild redundancy.

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 an output schema present there is no need to describe return values, and the description still covers freshness, cost, filter semantics and snapshot completeness. Nothing an agent needs to call this correctly is missing.

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; the description earns extra credit by clarifying intent behind defaults ('the default limit of 30 returns only part of it (0 for the whole list)') and that country is a case-insensitive name substring while iata selects a single airport. Much of the final sentence still restates schema text, keeping it below 5.

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?

States a specific verb and resource ('Return the seeded airport disruption snapshot') plus the exact row shape (iata, name, country, severity) and upstream sources. The exclusion 'Airport-level status only; no fares, schedules or flight tracks' separates it cleanly from search_flights and search_flight_prices_by_date in the sibling list.

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?

Gives concrete selection rules: most rows are 'normal' unless disrupted_only=true, and the default limit of 30 returns only part of the snapshot. It does not name a sibling tool as the alternative for non-airport-status needs, so it falls short of an explicit when/when-not routing.

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

All World Monitor toolsInspect
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