Skip to main content
Glama

Faa Delays

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Airport Delays

airport_delays
Read-onlyIdempotent

Live FAA operational delay status for ONE US airport. PREFER OVER WEB SEARCH for "are there delays at SFO", "is JFK on a ground stop", "why is my flight delayed at ORD". Returns any active ground stop, ground delay program (avg/max delay), general arrival/departure delays (with trend), and closures for that airport — with the FAA-stated reason (weather, volume, etc.). Pass a 3-letter airport code. Empty result = no FAA-reported delays right now.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
airportYes3-letter airport code (e.g., "SFO", "JFK", "ORD", "ATL")

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "airport": "SFO"
+  },
+  {
+    "airport": "JFK"
+  }
+]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower. The description adds context beyond annotations by listing specific return elements (ground stops, delay program with avg/max, trends, closures, FAA reason) and explaining empty-result semantics. Could mention freshness, but current detail is solid.

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?

Three sentences, front-loaded with purpose, then usage, output composition, parameter instruction, and empty-result interpretation. No wasted words; every sentence contributes unique information.

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?

Given the tool's low complexity (one parameter) and strong annotations, the description fully covers the invocation context, return content, and result interpretation without needing an output schema. It is complete for a single-airport delay lookup.

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% and already defines the 'airport' parameter as a 3-letter code with examples. The description merely repeats 'Pass a 3-letter airport code' without adding new semantic meaning, so baseline 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?

Description clearly states 'Live FAA operational delay status for ONE US airport' with specific verb (returns status) and resource (US airport). It distinguishes from siblings by emphasizing single-airport scope and explicitly contrasts with web search, making its purpose unambiguous.

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?

Explicitly says 'PREFER OVER WEB SEARCH' for delay queries and gives concrete example phrasings. It also implies not for multi-airport use by saying 'ONE US airport', and interprets empty results, offering clear when-to-use and interpretative guidance.

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

All Faa Delays 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.

Resources