Related Servers

Most tools target a clearly distinct resource+action, and the descriptions proactively disambiguate the riskiest near-neighbours (fa_search_flights vs fa_search_flights_advanced vs fa_search_flight_positions, fa_get_flights vs fa_get_flight_history via the recent/historical distinction). A few pairs remain easy to confuse: fa_resolve_flight/fa_resolve_airport overlap with fa_get_flights/fa_get_airport, and the result-shape difference between position search and flight search must be inferred from prose rather than names.

Every tool carries the same fa_ prefix and follows a verb_noun snake_case pattern (fa_get_flight_track, fa_list_operators, fa_create_alert), with resource-scoped variants (fa_get_airport_flights, fa_get_operator_flights) staying readable. The only notable deviation is fa_healthcheck, which omits the verb, but it is a single diagnostic outlier and not confusing.

34 tools is heavy for a single API wrapper and sits well above the comfortable 3-15 band, even though the domain (flights, airports, operators, alerts, search grammars) is genuinely broad. Several entries feel like thin variations that could be folded into a mode/parameter—fa_count_flights, fa_resolve_flight, fa_resolve_airport, fa_search_flights vs fa_search_flights_advanced—so the surface is larger than strictly necessary.

Coverage is strong: alerts have full lifecycle CRUD plus webhook endpoint get/set, flights cover position, track, route, map, history, search, count and resolve, and airports/operators each get detail, list, flight board and near/route/weather extras. Gaps are minor but real—no aircraft-type/airframe detail lookup beyond owner, no operator-level route statistics, and no airport/runway or surface data.