flightradar24-mcp-server

search_flights

Read-only

Search live airborne flights by route, airline, aircraft type, registration, altitude, or geographic area. Get real-time positions and flight details from Flightradar24.

Instructions

Search for currently airborne flights using the FR24 live flight positions endpoint. At least one filter (besides limit and detail_level) must be provided.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of results to return (default: 10, max: 30000).
`route`	No	Route(s) between airports or countries, comma-separated (e.g., 'JFK-LAX'). Max 15.
`bounds`	No	Geographic bounds to search within
`airline_icao`	No	ICAO airline code the aircraft is operating as (e.g., 'BAW' for British Airways). IATA airline codes are not supported by the FR24 API for this filter.
`detail_level`	No	Amount of detail to return. "full" (default) includes route, registration, and aircraft type; "light" returns only position data and costs fewer FR24 API credits.
`registration`	No	Aircraft registration(s), comma-separated (e.g., 'G-EUPT'). Max 15.
`aircraft_type`	No	ICAO aircraft type code(s), comma-separated (e.g., 'A320'). Max 15.
`altitude_range`	No	Altitude range(s) in feet (e.g., '0-3000' or '0-3000,30000-40000').

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`flights`	Yes
`message`	No
`timestamp`	Yes
`search_params`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Sep 20, 2026

TDQS

A4/5.0

Behavior4/5

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

With readOnlyHint=true and openWorldHint=true annotations already covering the safety profile, the description adds useful context: the tool targets currently airborne flights and enforces a filter requirement. This goes beyond the annotations without contradicting them.

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?

Two tight sentences with no filler. The key scoping detail ('currently airborne', 'FR24 live flight positions endpoint') is front-loaded, and the validation constraint is stated directly.

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 rich input schema, output schema, and read-only annotations, the description is largely complete for calling the tool correctly. The only notable gap is not mentioning sibling tools or when another endpoint would be more appropriate.

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 every parameter thoroughly. The description adds only a global filter requirement and does not enrich individual parameter meaning; baseline 3 is appropriate.

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 names a specific verb and resource ('Search for currently airborne flights using the FR24 live flight positions endpoint') and the 'currently airborne' scope helps set it apart from flight-data lookup siblings. It does not explicitly name a sibling alternative, so it misses the top tier for differentiation.

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 gives a clear context (searching currently airborne flights) and an explicit, operational constraint: at least one actual filter must be provided. It does not state when to prefer a sibling such as get_flights_in_zone, so there is no exclusion guidance.

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

Deploy Server