Skip to main content
Glama
BACH-AI-Tools

Flightradar24 MCP Server

get_historic_flights_count

Count historical aircraft flight positions by specifying a timestamp and search parameters like flight numbers, airports, or aircraft types to analyze past aviation activity.

Instructions

Returns number of historical aircraft flight positions. IMPORTANT: Timestamp is required, and at least one additional search parameter (other than limit) must be provided and non-empty.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boundsNoCoordinates defining an area. Order: north, south, west, east (comma-separated float values).
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>. Directions: inbound, outbound, both.
routesNoFlights between airports/countries (e.g., SE-US, ESSA-JFK). Max 15.
aircraftNoAircraft ICAO type codes (comma-separated, max 15).
altitude_rangesNoFlight altitude ranges in feet (e.g., 0-3000, 5000-7000).
squawksNoSquawk codes in hex format (comma-separated).
categoriesNoCategories of Flights (comma-separated: P, C, M, J, T, H, B, G, D, V, O, N).
data_sourcesNoSource of information (comma-separated: ADSB, MLAT, ESTIMATED).
airspacesNoFlight information region in lower or upper airspace.
gspeedNoFlight ground speed in knots (single value or range, e.g., 120-140, 80).
limitNoLimit of results. Recommended, unless needed. Max 30000.
timestampYesUnix timestamp for the historical snapshot.

Implementation Reference

  • Handler function registered for the 'get_historic_flights_count' MCP tool. Validates parameters, extracts timestamp, cleans optional params, fetches count from FR24Client, and returns formatted text response.
    server.tool(
      'get_historic_flights_count',
      'Returns number of historical aircraft flight positions. IMPORTANT: Timestamp is required, and at least one additional search parameter (other than limit) must be provided and non-empty.',
      historicFlightPositionsCountSchema.shape,
      async (params: z.infer<typeof historicFlightPositionsCountSchema>) => {
        try {
          validateHasRequiredParams(params, ['timestamp', 'limit']);
          const { timestamp, ...restParams } = params;
          const cleanedOptionalParams = cleanParams(restParams);
          const result = await fr24Client.getHistoricPositionsCount({ timestamp, ...cleanedOptionalParams });
          return {
            content: [{
              type: 'text' as const,
              text: `Historic flight count at timestamp ${timestamp}: ${result.record_count}`
            }]
          };
        } catch (error) {
          return {
            content: [{
              type: 'text' as const,
              text: `Error: ${error instanceof Error ? error.message : 'Unknown error'}`
            }],
            isError: true
          };
        }
      }
    );
  • Zod input schema for the get_historic_flights_count tool, extending baseFlightPositionsSchema with required timestamp.
    const historicFlightPositionsCountSchema = baseFlightPositionsSchema.extend({
      timestamp: z.number().describe('Unix timestamp for the historical snapshot.')
    });
  • Base Zod schema for flight positions queries used by multiple tools, including get_historic_flights_count via extension.
    const baseFlightPositionsSchema = z.object({
      bounds: z.string().min(1).optional().describe('Coordinates defining an area. Order: north, south, west, east (comma-separated float values).'),
      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>. Directions: inbound, outbound, both.'),
      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).'),
      altitude_ranges: z.string().min(1).optional().describe('Flight altitude ranges in feet (e.g., 0-3000, 5000-7000).'),
      squawks: z.string().min(1).optional().describe('Squawk codes in hex format (comma-separated).'),
      categories: z.string().min(1).optional().describe('Categories of Flights (comma-separated: P, C, M, J, T, H, B, G, D, V, O, N).'),
      data_sources: z.string().min(1).optional().describe('Source of information (comma-separated: ADSB, MLAT, ESTIMATED).'),
      airspaces: z.string().min(1).optional().describe('Flight information region in lower or upper airspace.'),
      gspeed: z.string().min(1).optional().describe('Flight ground speed in knots (single value or range, e.g., 120-140, 80).'),
      limit: z.number().optional().describe('Limit of results. Recommended, unless needed. Max 30000.')
  • FR24Client helper method that performs the HTTP request to the FR24 API endpoint for historic flight positions count.
    async getHistoricPositionsCount(params: HistoricFlightPositionsCountQueryParams): Promise<RecordCountResponse> {
      return this.makeRequest<RecordCountResponse>('/historic/flight-positions/count', params);
    }
  • Helper function used in the handler to validate that required parameters are provided.
    // Helper function to validate that at least one meaningful parameter is provided
    function validateHasRequiredParams(params: Record<string, any>, excludeKeys: string[] = ['limit']): void {
      const meaningfulParams = Object.entries(params).filter(([key, value]) => 
        !excludeKeys.includes(key) && 
        value !== null && 
        value !== undefined && 
        value !== ''
      );
      
      if (meaningfulParams.length === 0) {
        throw new Error(`At least one parameter other than ${excludeKeys.join(', ')} must be provided and non-empty. Available parameters: ${Object.keys(params).filter(k => !excludeKeys.includes(k)).join(', ')}`);
      }
    }
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that timestamp is required and at least one additional parameter is needed, which are important behavioral constraints. However, it doesn't mention rate limits, authentication requirements, data freshness, or what happens when no results match the criteria. For a tool with 17 parameters and no annotations, this leaves significant behavioral 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 extremely concise and well-structured. The first sentence states the purpose, and the second sentence provides critical usage constraints. Every word earns its place, with no redundant information. It's front-loaded with the core functionality followed by essential requirements.

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 (17 parameters, no annotations, no output schema), the description is incomplete. While it covers the basic purpose and parameter requirements, it doesn't explain what the return value looks like (just 'number' without format), error conditions, or how the count relates to the filtering parameters. For a count tool with rich filtering options, more context about the counting methodology would be helpful.

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 17 parameters thoroughly. The description adds minimal value beyond the schema by emphasizing that timestamp is required and at least one other parameter (excluding limit) must be provided. This provides some context about parameter dependencies but doesn't add semantic meaning to individual parameters beyond what's in the schema.

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's purpose: 'Returns number of historical aircraft flight positions.' It specifies the resource (historical aircraft flight positions) and verb (returns number). However, it doesn't explicitly differentiate from sibling tools like 'get_historic_flights_positions_full' or 'get_flight_summary_count', which might offer similar functionality with different output formats.

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 usage guidance: 'Timestamp is required, and at least one additional search parameter (other than limit) must be provided and non-empty.' This tells the agent when to use this tool (for historical counts with timestamp and at least one filter). However, it doesn't specify when to choose this tool over alternatives like 'get_historic_flight_events_full' or 'get_live_flights_count'.

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