Skip to main content
Glama
Pradumnasaraf

Aviationstack MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_flight_statusA

Look up one specific flight by its IATA flight number, for the current day or a given date. Returns flight status plus scheduled, estimated and actual times, terminal, gate, baggage belt and delay minutes for both ends, with the operating flight ordered ahead of its codeshares. Use this when the question names a flight number; use flights_with_airline to browse an airline's flights, or historical_flights_by_date for past dates.

flights_with_airlineA

Return live flights for one airline, optionally narrowed to a single flight status. Returns flight number, airline, departure and arrival airports with timezones, scheduled departure time, status, delay, terminal and gate. Use this to survey an airline's current activity; use get_flight_status when you already know the flight number.

historical_flights_by_dateA

Return flights that already operated on a past date, with optional airline and route filters. Returns flight date, status, flight number, airline, and both airports with their scheduled times. Requires the Basic plan or higher. Use this for past dates only: use flight_arrival_departure_schedule for today and future_flights_arrival_departure_schedule for later dates.

flight_arrival_departure_scheduleA

Return today's arrival or departure board for an airport, optionally filtered by airline name. Returns airline, flight number, scheduled, estimated and actual times, terminals, gates and departure delay per flight. Covers the current day only: for any later date use future_flights_arrival_departure_schedule instead.

future_flights_arrival_departure_scheduleA

Return the scheduled arrival or departure board for an airport on a specific future date. Covers any date from tomorrow through about 12 months ahead, including the next 7 days. Returns airline, flight number, scheduled times, arrival airport, terminal, gate and aircraft model. Use flight_arrival_departure_schedule for today's board instead.

random_aircraft_typeA

Return a random sample of aircraft types from the Aviationstack reference catalog. Each record has aircraft_name and iata_code. Records are drawn from a random offset, so repeated calls return different rows. This samples the catalog and cannot look up a specific model: there is no search parameter.

random_airplanes_detailed_infoA

Return a random sample of individual airplanes from the reference catalog. Each record has model name and code, series, production line, registration number, owner, age, engine type and count, delivery date and first flight date. Records are drawn from a random offset, so repeated calls return different aircraft. Sampling only: there is no lookup by registration.

random_countries_detailed_infoA

Return a random sample of countries from the reference catalog. Each record has country name, capital, continent, ISO2, ISO3 and numeric ISO codes, FIPS code, currency name and code, phone prefix and population. Records are drawn from a random offset, so repeated calls return different countries. Sampling only: there is no lookup by country name or code.

random_cities_detailed_infoA

Return a random sample of cities from the reference catalog. Each record has city name, IATA code, country ISO2, latitude, longitude, timezone, GMT offset and geoname id. Records are drawn from a random offset, so repeated calls return different cities. Sampling only: there is no lookup by city name.

list_airportsA

List airports from the reference catalog, one page at a time, with optional text search. Each record has airport name, IATA and ICAO codes, city IATA code, country name and ISO2, timezone and GMT offset, alongside a pagination block carrying limit, offset and total. Use search to resolve an airport name to the IATA code the flight tools expect.

list_airlinesA

List airlines from the reference catalog, one page at a time, with optional text search. Each record has airline name, IATA and ICAO codes, callsign, operational status, country name and ISO2, alongside a pagination block carrying limit, offset and total. Use search to resolve an airline name to the IATA code the flight tools expect.

list_routesA

List scheduled routes, one page at a time, filtered by any combination of airline, departure airport and arrival airport. Each record has airline IATA and ICAO codes, flight number, and departure and arrival airport codes, alongside a pagination block carrying limit, offset and total. This says which routes exist, not whether a flight is operating: use get_flight_status for that. Requires the Basic plan or higher.

list_taxesA

List aviation taxes from the reference catalog, one page at a time, with optional text search. Each record has tax id, tax name and the associated IATA code, alongside a pagination block carrying limit, offset and total. This is static reference data, not fares or amounts charged on a booking. Requires a paid plan.

Prompts

Interactive templates invoked by user choice

NameDescription
plan_flight_status_lookupGenerate a plan for checking the status of one specific flight.
plan_airline_flight_lookupGenerate a concise plan for querying live flights for an airline.
plan_future_schedule_lookupGenerate a plan for querying an airport's scheduled arrival or departure board on a future date, from tomorrow through about 12 months ahead.
plan_reference_data_lookupGenerate a plan for exploring airport/airline/route/tax reference data.

Resources

Contextual data attached and managed by the client

NameDescription
server_metadataStatic metadata about this Aviationstack MCP server.
aviationstack_endpointsAvailable Aviationstack API endpoints used by tools.

TDQS

A4.3/5.0

Scored across 13 tools

Disambiguation4/5

Most tools have clearly distinct purposes, especially the time-scoped flight tools (today, future, past) and the reference list tools. The two random aircraft tools could be confused at a glance, but their descriptions clearly separate aircraft types from individual airplanes.

Naming Consistency4/5

The tool names mostly follow consistent snake_case patterns: get_ for single lookups, list_ for catalog pages, and random_ for sampling tools. A few names like flights_with_airline and flight_arrival_departure_schedule deviate from the verb_noun pattern, but the overall convention remains readable and predictable.

Tool Count5/5

Thirteen tools is a well-scoped size for a flight data API covering flight status, schedules, and reference data. Each tool has a defined role, and the count is neither bloated nor too thin.

Completeness4/5

The server covers the core flight workflows well: specific flight status, airline flight lists, today's/future/historical schedules, and route/reference lookups. Minor gaps exist, such as no specific lookup for random catalog entities beyond sampling, but agents can complete most flight-status tasks without dead ends.

Maintenance

ActivityMaintained
ResponsivenessSlow