Skip to main content
Glama
BACH-AI-Tools

Flightradar24 MCP Server

get_flight_summary_light

Retrieve flight summaries with key timings, locations, aircraft details, and operator information for real-time or historical aviation data queries.

Instructions

Returns key timings and locations of aircraft takeoffs and landings alongside all primary flight, aircraft, and operator information. Both real-time and historical data are available. Data is available starting from 2024-04-07 and will be extended further in the near future. IMPORTANT: flight_datetime_from and flight_datetime_to are required, and at least one additional search parameter (other than sort and limit) should be provided.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
flight_datetime_fromYesStart datetime (YYYY-MM-DDTHH:MM:SSZ). Requires flight_datetime_to. Cannot be used with flight_ids.
flight_datetime_toYesEnd datetime (YYYY-MM-DDTHH:MM:SSZ). Requires flight_datetime_from. Cannot be used with flight_ids.
flightsNoFlight numbers (comma-separated values, max 15).
callsignsNoFlight callsigns (comma-separated values, max 15).
registrationsNoAircraft registration numbers (comma-separated values, max 15).
painted_asNoAircraft painted in an airline's livery (ICAO code, comma-separated, max 15).
operating_asNoAircraft operating under an airline's call sign (ICAO code, comma-separated, max 15).
airportsNoAirports (IATA/ICAO/ISO 3166-1 alpha-2) or countries. Use format: [direction:]<code>.
routesNoFlights between airports/countries (e.g., SE-US, ESSA-JFK). Max 15.
aircraftNoAircraft ICAO type codes (comma-separated, max 15).
sortNoSorting order by first_seen (default: asc).
limitNoLimit of results. Recommended, unless needed. Max 20000.

Implementation Reference

  • Core handler function in FR24Client class that performs the HTTP request to the FR24 API endpoint '/flight-summary/light' using the shared makeRequest method, returning FlightSummaryLight[].
    async getFlightSummaryLight(params: Record<string, any>): Promise<FlightSummaryLight[]> {
      return this.makeRequest<FlightSummaryLight[]>('/flight-summary/light', params);
    }
  • Zod schema defining the input parameters for the get_flight_summary_light tool (shared with full version), including required date range and optional filters.
    const flightSummaryToolParamsSchema = z.object({
      flight_datetime_from: z.string().min(1).describe('Start datetime (YYYY-MM-DDTHH:MM:SSZ). Requires flight_datetime_to. Cannot be used with flight_ids.'),
      flight_datetime_to: z.string().min(1).describe('End datetime (YYYY-MM-DDTHH:MM:SSZ). Requires flight_datetime_from. Cannot be used with flight_ids.'),
      flights: z.string().min(1).optional().describe('Flight numbers (comma-separated values, max 15).'),
      callsigns: z.string().min(1).optional().describe('Flight callsigns (comma-separated values, max 15).'),
      registrations: z.string().min(1).optional().describe('Aircraft registration numbers (comma-separated values, max 15).'),
      painted_as: z.string().min(1).optional().describe("Aircraft painted in an airline's livery (ICAO code, comma-separated, max 15)."),
      operating_as: z.string().min(1).optional().describe("Aircraft operating under an airline's call sign (ICAO code, comma-separated, max 15)."),
      airports: z.string().min(1).optional().describe('Airports (IATA/ICAO/ISO 3166-1 alpha-2) or countries. Use format: [direction:]<code>.'),
      routes: z.string().min(1).optional().describe('Flights between airports/countries (e.g., SE-US, ESSA-JFK). Max 15.'),
      aircraft: z.string().min(1).optional().describe('Aircraft ICAO type codes (comma-separated, max 15).'),
      sort: z.enum(['asc', 'desc']).optional().describe('Sorting order by first_seen (default: asc).'),
      limit: z.number().optional().describe('Limit of results. Recommended, unless needed. Max 20000.')
    });
  • src/server.ts:309-334 (registration)
    MCP tool registration using server.tool(), specifying name, description, input schema, and handler wrapper that validates inputs, cleans parameters, delegates to FR24Client handler, and formats the response as text content.
    server.tool(
      'get_flight_summary_light',
      'Returns key timings and locations of aircraft takeoffs and landings alongside all primary flight, aircraft, and operator information. Both real-time and historical data are available. Data is available starting from 2024-04-07 and will be extended further in the near future. IMPORTANT: flight_datetime_from and flight_datetime_to are required, and at least one additional search parameter (other than sort and limit) should be provided.',
      flightSummaryToolParamsSchema.shape,
      async (params: z.infer<typeof flightSummaryToolParamsSchema>) => {
         try {
          validateHasRequiredParams(params, ['flight_datetime_from', 'flight_datetime_to', 'sort', 'limit']);
          const cleaned = cleanParams(params);
          const result = await fr24Client.getFlightSummaryLight(cleaned);
          return {
            content: [{
              type: 'text' as const,
              text: `Found ${result.length} flight summaries (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
          };
        }
      }
    );
  • Shared helper method in FR24Client for making authenticated HTTP requests to FR24 API endpoints, handling various response structures and errors. Used by getFlightSummaryLight.
    private async makeRequest<T>(endpoint: string, params?: Record<string, any>): Promise<T> {
      try {
        console.log(`Making request to ${endpoint} with params: ${JSON.stringify(params)}`);
        const response = await axios.get(`${this.baseUrl}${endpoint}`, {
          params: params,
          headers: {
            'Accept': 'application/json',
            'Accept-Version': 'v1',
            'Authorization': `Bearer ${this.apiKey}`
          }
        });
        // Handle responses nested under 'data' key, except for count endpoints and single objects
        if (response.data && response.data.data && Array.isArray(response.data.data)) {
          return response.data.data as T;
        }
        // Handle count responses
        if (response.data && typeof response.data.record_count === 'number') {
          return response.data as T;
        }
        // Handle single object responses (like flight tracks, airport info, airline info)
        if (response.data && typeof response.data === 'object' && !Array.isArray(response.data)) {
            return response.data as T;
        }
        // Fallback for unexpected structure
        return response.data as T;
      } catch (error) {
        const message = error instanceof AxiosError ? error.message : 'Unknown error';
        console.error(`API Request Failed: ${endpoint}`, error);
        throw new Error(`Failed request to ${endpoint}: ${message}`);
      }
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions data availability starting from 2024-04-07 and future extensions, which adds useful context. However, it lacks details on rate limits, authentication needs, error handling, or pagination behavior, leaving gaps for a tool with 12 parameters.

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?

The description is well-structured and front-loaded with the core purpose, followed by data availability details and important usage notes. It's concise with three sentences that each serve a clear purpose, though it could be slightly more streamlined by integrating the date requirement into the initial sentence.

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?

Given the complexity (12 parameters, no output schema, no annotations), the description is moderately complete. It covers the purpose, data scope, and key usage rules, but lacks details on output format, error cases, or performance considerations, which would be helpful for a tool with many search options.

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 documents all parameters thoroughly. The description adds value by emphasizing that 'flight_datetime_from and flight_datetime_to are required, and at least one additional search parameter (other than sort and limit) should be provided,' which clarifies usage constraints beyond the schema's required fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool returns 'key timings and locations of aircraft takeoffs and landings alongside all primary flight, aircraft, and operator information,' which is specific about the data returned. However, it doesn't explicitly differentiate this 'light' version from sibling tools like 'get_flight_summary_full' or 'get_flight_summary_count,' leaving some ambiguity about scope differences.

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 for usage by stating 'Both real-time and historical data are available' and specifying date range requirements and additional parameter needs. It doesn't explicitly mention when to use this tool versus alternatives like 'get_flight_summary_full' or 'get_flight_summary_count,' but the naming and data scope imply it's a summary-focused tool.

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