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

Name	Required	Description	Default
`flight_ids`	Yes	Comma-separated fr24_ids (maximum 15 IDs). Cannot be combined with event_datetime.
`event_types`	Yes	Event 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
      };
    }
  }
);

src/server.ts:97-100 (schema)

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.')
});

src/fr24-client.ts:114-116 (handler)

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);
}

src/types.ts:207-210 (schema)

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'
}

src/types.ts:235-246 (schema)

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[];
}

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Dec 11, 2025

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries the transparency burden. It discloses that events are sorted by event_timestamp and grouped by flight_id, and that inputs must be non-empty. However, it omits return format, pagination, permissions, or potential error cases, which are important behavioral details.

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 two concise sentences: the first states the core functionality and output characteristics, the second conveys a key constraint. It is front-loaded, free of fluff, and well-structured.

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?

The description covers the essential what-it-does and sorting/grouping behavior, but lacks details on return structure, which is notable since no output schema exists. It also does not clarify the difference from the 'light' sibling tool, making the description average in completeness.

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?

The input schema already provides 100% coverage with descriptions for both parameters, including the list of event types and the max ID limit. The description additionally emphasizes that both parameters are required and non-empty, but does not add meaningfully beyond the schema.

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 returns selected historical flight events with specific event types, detailed information, sorted and grouped. This distinguishes it from sibling tools like position checkers and the 'light' version by emphasizing detail and event categories.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool versus alternatives such as get_historic_flight_events_light or position tools. The only guidance is a required-parameter note, which is more of a validation rule than usage context.

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

Deploy Server