Skip to main content
Glama

get_historic_flight_events_light

Retrieve historical flight events like takeoff, landing, and gate transitions for specific flights using Flightradar24 data.

Instructions

Returns selected historical flight events (gate_departure, takeoff, cruising, airspace_transition, resuming_flightplan, descent, landed, gate_arrival), sorted by event_timestamp and grouped by flight_id. REQUIRED: flight_ids and event_types must be provided and non-empty.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
flight_idsYesComma-separated fr24_ids (maximum 15 IDs). Cannot be combined with event_datetime.
event_typesYesEvent types to filter by (comma-separated values). Available values: all, gate_departure, takeoff, cruising, airspace_transition, descent, landed, gate_arrival.

Implementation Reference

  • Core implementation of the getHistoricFlightEventsLight method, which invokes the makeRequest helper to fetch light historic flight events from the FR24 API endpoint '/historic/flight-events/light'.
    async getHistoricFlightEventsLight(params: HistoricFlightEventsQueryParams): Promise<HistoricFlightEventsLight[]> { return this.makeRequest<HistoricFlightEventsLight[]>('/historic/flight-events/light', params); }
  • Zod input schema for validating tool parameters: flight_ids (comma-separated FR24 flight IDs) and event_types.
    const historicFlightEventsSchema = z.object({ flight_ids: z.string().min(1).describe('Comma-separated fr24_ids (maximum 15 IDs). Cannot be combined with event_datetime.'), event_types: z.string().min(1).describe('Event types to filter by (comma-separated values). Available values: all, gate_departure, takeoff, cruising, airspace_transition, descent, landed, gate_arrival.') });
  • src/server.ts:498-522 (registration)
    MCP server tool registration for 'get_historic_flight_events_light', including description, input schema reference, and the handler function that delegates to FR24Client.
    server.tool( 'get_historic_flight_events_light', 'Returns selected historical flight events (gate_departure, takeoff, cruising, airspace_transition, resuming_flightplan, descent, landed, gate_arrival), sorted by event_timestamp and grouped by flight_id. REQUIRED: flight_ids and event_types must be provided and non-empty.', historicFlightEventsSchema.shape, async (params: z.infer<typeof historicFlightEventsSchema>) => { try { console.log(`Raw params received by handler: ${JSON.stringify(params)}`); const result = await fr24Client.getHistoricFlightEventsLight(params); return { content: [{ type: 'text' as const, text: `Found ${result.length} flights with historic events (light details):\n${JSON.stringify(result, null, 2)}` }] }; } catch (error) { return { content: [{ type: 'text' as const, text: `Error: ${error instanceof Error ? error.message : 'Unknown error'}` }], isError: true }; } } );
  • TypeScript type definition for input parameters matching the Zod schema.
    export interface HistoricFlightEventsQueryParams { flight_ids: string; // Required, comma-separated fr24_ids (maximum 15 IDs) event_types: string; // Required, comma-separated event types or 'all' }
  • TypeScript type definition for the light output response structure containing flight ID, callsign, hex, and list of events.
    export interface HistoricFlightEventsLight { fr24_id: string; callsign: string; hex: string; events: FlightEvent[]; }

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/BACH-AI-Tools/fr24api-mcp'

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