Skip to main content
Glama
BACH-AI-Tools

Flightradar24 MCP Server

get_historic_flight_events_full

Retrieve detailed historical flight events including gate departures, takeoffs, landings, and airspace transitions for specific flights, providing comprehensive timeline data for aviation analysis.

Instructions

Returns selected historical flight events (gate_departure, takeoff, cruising, airspace_transition, resuming_flightplan, descent, landed, gate_arrival), with detailed information, 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

  • src/server.ts:472-496 (registration)
    MCP server.tool registration for the 'get_historic_flight_events_full' tool, including description, input schema, and execution handler.
    server.tool(
      'get_historic_flight_events_full',
      'Returns selected historical flight events (gate_departure, takeoff, cruising, airspace_transition, resuming_flightplan, descent, landed, gate_arrival), with detailed information, 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.getHistoricFlightEventsFull(params);
          return {
            content: [{
              type: 'text' as const,
              text: `Found ${result.length} flights with historic events (full 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
          };
        }
      }
    );
  • Zod schema for validating tool input 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.')
    });
  • FR24Client class method implementing the core logic to fetch full historic flight events from the FR24 API endpoint.
    async getHistoricFlightEventsFull(params: HistoricFlightEventsQueryParams): Promise<HistoricFlightEventsFull[]> {
      return this.makeRequest<HistoricFlightEventsFull[]>('/historic/flight-events/full', params);
    }
  • TypeScript interface defining the query parameters type used by the FR24 client handler.
    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 interface defining the structure of the full historic flight events response.
    export interface HistoricFlightEventsFull {
      fr24_id: string;
      callsign: string;
      hex: string;
      operating_as: string;
      painted_as: string;
      orig_iata: string;
      orig_icao: string;
      dest_iata: string;
      dest_icao: string;
      events: FlightEvent[];
    }
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses that the tool returns sorted and grouped data, which is valuable behavioral context. However, it doesn't mention rate limits, authentication needs, error conditions, pagination, or what constitutes 'detailed information' beyond the event types listed. The description adds some behavioral insight but leaves significant gaps.

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 efficiently structured in two sentences: the first states the purpose and key characteristics, the second specifies requirements. Every element serves a clear purpose with no redundant information. The event type list is appropriately included for clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only query tool with 2 parameters and 100% schema coverage, the description provides adequate purpose and requirements. However, without annotations or output schema, it should ideally describe the return format more explicitly (what 'detailed information' includes) and mention any constraints like rate limits. The sibling context suggests this is part of a flight data API where such details matter.

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 description coverage is 100%, so the schema already fully documents both parameters. The description adds the requirement that parameters must be 'non-empty' and implies they work together, but doesn't provide additional semantic context beyond what's in the schema descriptions. This meets the baseline for high schema coverage.

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 specific action ('Returns selected historical flight events'), identifies the resource ('historical flight events'), and lists the specific event types included. It distinguishes itself from sibling 'get_historic_flight_events_light' by specifying 'with detailed information' and the grouping/sorting approach.

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

Usage Guidelines4/5

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

The description provides clear context about when to use this tool (for historical flight events with detailed information), and the REQUIRED section indicates mandatory parameters. However, it doesn't explicitly contrast when to use this versus the 'light' version or other flight-related tools, nor does it mention any exclusions or prerequisites beyond parameter requirements.

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

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