Skip to main content
Glama
airlabs-co

AirLabs MCP Server

Official
by airlabs-co

get_flight_status

Retrieve live status of a specific flight number, including scheduled/actual times, terminal, gate, delays, and aircraft details.

Instructions

TRIGGER: use automatically (no need for the user to mention 'AirLabs') whenever they ask about the status, arrival/departure time, gate, terminal, or delay of a SPECIFIC flight number — e.g. 'is BA117 on time?', 'when does LH401 land?', 'my flight AA6'. Get the live status of ONE flight by its flight number. Returns scheduled/estimated/actual departure & arrival times, status (scheduled/en-route/landed), terminal, gate, baggage belt, delay minutes, codeshare info, and aircraft details. Returns only the single closest live/scheduled/landed instance of that number. USE CASES: 'Is BA117 on time?', 'What gate is LH401?', 'Will my flight be late?'. INPUT: requires flight_iata OR flight_icao. If the user gives an airline NAME plus a number (e.g. 'Wizz Air 4321'), first call get_airline_info(name) to get the IATA code (W6) and build the flight_iata ('W64321'). NOTE: for ALL daily instances of a recurring number, use get_airport_schedule with flight_iata instead — this tool returns only one.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_fieldsNoComma-separated fields to return, to keep the response small, e.g. 'status,arr_estimated,arr_delayed,arr_terminal,arr_gate'.
flight_iataNoFlight IATA code-number, e.g. 'BA117', 'AA6'.
flight_icaoNoFlight ICAO code-number, e.g. 'BAW117'. Alternative to flight_iata.
Behavior4/5

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

No annotations provided, but description reveals key behavior: returns only single closest live/scheduled/landed instance, non-destructive read operation. Could mention rate limits, but not required.

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?

Structured with TRIGGER, INPUT, NOTE blocks for readability. Slightly lengthy but each sentence adds unique value. Front-loaded with trigger conditions.

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 3 parameters and no output schema, the description fully covers return fields, single-instance behavior, alternative tool reference, and a prerequisite step. No gaps.

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%, but description adds value by explaining the alternative parameters (flight_iata vs flight_icao) with example formats, and the _fields parameter for response trimming.

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 'Get the live status of ONE flight by its flight number' and lists return fields, distinguishing it from siblings like get_airport_schedule which returns multiple instances.

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 defines TRIGGER for automatic use, provides example use cases, and states when NOT to use this tool (use get_airport_schedule for daily instances). Also gives a prerequisite step for airline name conversion.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/airlabs-co/airlabs-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server