Skip to main content
Glama

Get Flight Status

amadeus.flights.status
Read-onlyIdempotent

Retrieve real-time flight status updates—delays, cancellations, gate changes—for any flight using airline code, flight number, and date.

Instructions

Get real-time status of a specific flight — delays, cancellations, gate info (Amadeus)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
carrier_codeYesAirline IATA or ICAO code (e.g. AA, UAL)
flight_numberYesFlight number (e.g. 100, 1234)
dateYesFlight date in YYYY-MM-DD format

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoTool response payload. Shape varies per tool — consult the tool description and inputSchema. May be an object, array, string, or number depending on the upstream provider response.
errorNoPresent only when the call failed. Includes error code, message, request_id, and any provider-specific extras.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Addedv1.5.0
  2. Removedv1.0.20
  3. Addedv1.0.15
  4. Removedv1.0.14
  5. Addedv1.0.6
  6. Removedv1.0.5
  7. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations declare the tool as read-only, non-destructive, and idempotent. The description adds value by detailing the specific information returned (delays, cancellations, gate info) and the source (Amadeus). It does not contradict annotations.

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?

The description is a single, front-loaded sentence that efficiently communicates the tool's purpose without unnecessary words.

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 presence of an output schema and the clarity of the description for a straightforward status lookup tool, the description provides sufficient context for an agent to select and invoke the tool correctly.

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 coverage is 100%, so the baseline is 3. The description adds no additional meaning to the parameters beyond what the schema already provides.

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 the tool's action: 'Get real-time status of a specific flight', and specifies the types of status information provided (delays, cancellations, gate info). It distinguishes from siblings like amadeus.flights.search and amadeus.flights.price by focusing on status rather than search or pricing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for checking the real-time status of a specific flight but does not explicitly state when to use this tool versus alternatives like amadeus.flights.search or other flight status tools. No exclusion criteria or prerequisites are mentioned.

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/whiteknightonhorse/APIbase'

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