Skip to main content
Glama
BACH-AI-Tools

Flightradar24 MCP Server

get_live_flights_positions_full

Retrieve real-time aircraft positions and flight details by specifying search parameters like flight numbers, callsigns, airports, or geographic bounds to track live aviation movements.

Instructions

Returns real-time aircraft flight movement information including latitude, longitude, speed, and altitude alongside key flight and aircraft information such as origin, destination, callsign, registration and aircraft type. IMPORTANT: At least one search parameter (other than limit) must be provided and non-empty. Choose from: bounds, flights, callsigns, registrations, painted_as, operating_as, airports, routes, aircraft, altitude_ranges, squawks, categories, data_sources, airspaces, gspeed.

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.

Implementation Reference

  • The MCP tool handler function that validates input parameters, cleans them, fetches full live flight positions from FR24Client, and returns a formatted text response with the data or error.
    async (params: z.infer<typeof liveFlightPositionsSchema>) => {
       try {
        validateHasRequiredParams(params, ['limit']);
        const cleaned = cleanParams(params);
        const result = await fr24Client.getLivePositionsFull(cleaned);
        return {
          content: [{
            type: 'text' as const,
            text: `Found ${result.length} flights (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 input parameters used by the get_live_flights_positions_full tool (baseFlightPositionsSchema, aliased as liveFlightPositionsSchema).
    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.')
    });
  • src/server.ts:144-169 (registration)
    MCP server tool registration for 'get_live_flights_positions_full', including name, description, input schema, and handler function.
    server.tool(
      'get_live_flights_positions_full',
      'Returns real-time aircraft flight movement information including latitude, longitude, speed, and altitude alongside key flight and aircraft information such as origin, destination, callsign, registration and aircraft type. IMPORTANT: At least one search parameter (other than limit) must be provided and non-empty. Choose from: bounds, flights, callsigns, registrations, painted_as, operating_as, airports, routes, aircraft, altitude_ranges, squawks, categories, data_sources, airspaces, gspeed.',
      liveFlightPositionsSchema.shape,
      async (params: z.infer<typeof liveFlightPositionsSchema>) => {
         try {
          validateHasRequiredParams(params, ['limit']);
          const cleaned = cleanParams(params);
          const result = await fr24Client.getLivePositionsFull(cleaned);
          return {
            content: [{
              type: 'text' as const,
              text: `Found ${result.length} flights (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
          };
        }
      }
    );
  • FR24Client helper method that makes the HTTP API request to fetch full live flight positions data.
    async getLivePositionsFull(params: LiveFlightPositionsQueryParams): Promise<FlightPositionFull[]> {
      return this.makeRequest<FlightPositionFull[]>('/live/flight-positions/full', params);
    }
  • TypeScript type definition for the full flight position data returned by the tool.
    export interface FlightPositionFull extends FlightPositionLight {
      flight: string;
      type: string;
      reg: string;
      painted_as: string;
      operating_as: string;
      orig_iata: string;
      orig_icao: string;
      dest_iata: string;
      dest_icao: string;
      eta: string; // ISO 8601 format
    }
Behavior4/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 effectively describes the tool's behavior: it returns real-time data (implying dynamic, current information) and lists the types of information included. However, it doesn't mention potential limitations like rate limits, data freshness, or error conditions (e.g., what happens if no flights match the filters). For a real-time data tool with no annotations, this is good but not exhaustive.

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: the first sentence clearly states the purpose and returned data, followed immediately by the critical usage requirement. Every sentence earns its place—the first explains what the tool does, and the second provides essential invocation guidance. No wasted words or redundant information.

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

Completeness4/5

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

Given the complexity (16 parameters, real-time data, no annotations, no output schema), the description does well. It clearly explains the tool's purpose, provides crucial usage rules, and lists available parameters. However, it doesn't describe the output format (e.g., structure of returned flight data) or potential behavioral aspects like pagination or error handling, which would be helpful given the absence of an output schema.

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 16 parameters thoroughly. The description adds value by emphasizing that at least one parameter (other than limit) must be provided, which is a critical semantic constraint not captured in the schema's property definitions. However, it doesn't provide additional context about parameter interactions or prioritization beyond what's in the schema descriptions.

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's purpose: 'Returns real-time aircraft flight movement information including latitude, longitude, speed, and altitude alongside key flight and aircraft information such as origin, destination, callsign, registration and aircraft type.' This specifies both the data returned (positional data plus flight metadata) and distinguishes it from sibling tools like 'get_live_flights_positions_light' (likely a lighter version) and 'get_historic_flights_positions_full' (historical vs real-time).

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

Usage Guidelines5/5

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

The description provides explicit usage guidance: 'IMPORTANT: At least one search parameter (other than limit) must be provided and non-empty. Choose from: bounds, flights, callsigns, registrations, painted_as, operating_as, airports, routes, aircraft, altitude_ranges, squawks, categories, data_sources, airspaces, gspeed.' This clearly states when to use the tool (when you need real-time flight positions with filtering) and the mandatory requirement for at least one filter parameter, which is critical for correct invocation.

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