Pro Flight Search Airport Delays
Server Details
Read-only airport delay, weather, and 24h forecast tools for AI assistants. Airport-level only.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.1/5 across 4 of 4 tools scored.
The two core functions (search airports and get delay status) are clearly distinct. Each function has an alias, but descriptions explicitly state they are aliases, so agents can confidently choose either without ambiguity.
Naming conventions are mixed: dot-notation (airport.get_delay_status) vs underscore (get_airport_delay_status), and one pair uses 'search_supported' while the other uses 'search_supported_airports'. No consistent pattern across the set.
Four tools for a focused domain (airport delays). The count is appropriate, though it includes two redundant alias tools, which slightly inflates the number without adding functionality.
The server covers the core functionality for airport delay information: searching for airports and retrieving live delay status. Minor gaps like historical data or flight-specific delays are outside the stated scope.
Available Tools
4 toolsairport.get_delay_statusGet airport delay statusRead-onlyIdempotentInspect
Get live airport-level delay, cancellation, weather flight-rules, and 24-hour forecast context for one airport. Accepts IATA code, city, or airport name. Alias of get_airport_delay_status for clients that prefer dot-notation tool names.
| Name | Required | Description | Default |
|---|---|---|---|
| format | No | Output format. Use plain for SMS-style replies; markdown includes formatted links. Defaults to plain. | |
| airport | Yes | Airport IATA code, city, or airport name. Examples: JFK, LHR, Copenhagen, Chicago O'Hare. |
Output Schema
| Name | Required | Description |
|---|---|---|
| scope | Yes | Current data scope for the tool result. |
| format | Yes | Returned text format. |
| airport | Yes | Resolved airport IATA code. |
| detailsUrl | Yes | Pro Flight Search airport details URL for citation or follow-up. |
| disclaimer | Yes | Operational-data disclaimer for the airport status. |
| statusText | Yes | Airport status text returned in the MCP content block. |
airport.search_supportedSearch supported airportsRead-onlyIdempotentInspect
Search Pro Flight Search tracked airports when a user's airport reference is ambiguous. Returns matching IATA codes to use with airport.get_delay_status. Alias of search_supported_airports for clients that prefer dot-notation tool names.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Airport code, city, or airport name to search. Examples: London, Paris, Chicago, ORD. |
Output Schema
| Name | Required | Description |
|---|---|---|
| query | Yes | Search query used to find tracked airports. |
| matches | Yes | Tracked airport matches that can be used with get_airport_delay_status or airport.get_delay_status. |
get_airport_delay_statusGet airport delay statusRead-onlyIdempotentInspect
Get live airport-level delay, cancellation, weather flight-rules, and 24-hour forecast context for one airport. Accepts IATA code, city, or airport name. Call this for questions like 'are there delays at JFK' or 'how is Copenhagen airport'. Airport-level only, not flight-number tracking.
| Name | Required | Description | Default |
|---|---|---|---|
| format | No | Output format. Use plain for SMS-style replies; markdown includes formatted links. Defaults to plain. | |
| airport | Yes | Airport IATA code, city, or airport name. Examples: JFK, LHR, Copenhagen, Chicago O'Hare. |
Output Schema
| Name | Required | Description |
|---|---|---|
| scope | Yes | Current data scope for the tool result. |
| format | Yes | Returned text format. |
| airport | Yes | Resolved airport IATA code. |
| detailsUrl | Yes | Pro Flight Search airport details URL for citation or follow-up. |
| disclaimer | Yes | Operational-data disclaimer for the airport status. |
| statusText | Yes | Airport status text returned in the MCP content block. |
search_supported_airportsSearch supported airportsRead-onlyIdempotentInspect
Search Pro Flight Search tracked airports when a user's airport reference is ambiguous. Returns matching IATA codes to use with get_airport_delay_status. Call this before airport status when the user says a city name like London or Chicago.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Airport code, city, or airport name to search. Examples: London, Paris, Chicago, ORD. |
Output Schema
| Name | Required | Description |
|---|---|---|
| query | Yes | Search query used to find tracked airports. |
| matches | Yes | Tracked airport matches that can be used with get_airport_delay_status or airport.get_delay_status. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!