Skip to main content
Glama

Related Servers

Alternatives to flightaware-mcp

No user-submitted related servers found.

    Related Servers

    TDQS

    B3.4/5.0

    Scored across 34 tools

    Disambiguation4/5

    Most tools target a distinct resource+action (flight track vs position vs route vs map, airport vs operator boards, alert CRUD). The search family is the weak spot: fa_search_flights, fa_search_flights_advanced, fa_search_flight_positions, fa_count_flights, and fa_foresight_search all overlap in intent and differ mainly by query grammar, which descriptions do explain but an agent can still easily misselect.

    Naming Consistency4/5

    Nearly all tools follow a consistent fa_verb_noun snake_case pattern (fa_get_flights, fa_list_airports, fa_create_alert, fa_delete_alert). Minor deviations exist: fa_healthcheck is noun-only and fa_foresight_search inverts the verb/noun order to noun_verb.

    Tool Count2/5

    34 tools is well above the range where a surface stays navigable for an agent, and several families (five search variants, four airport sub-resources) inflate the count. The underlying AeroAPI domain is broad, so the heavy count is defensible, but it still exceeds the ~15-tool sweet spot for coherent selection.

    Completeness4/5

    Coverage is broad and lifecycle-complete for most sub-domains: flights (get/search/track/route/history), airports (details, boards, delays, weather, counts, nearby, popular routes), operators, and alerts with full create/update/delete/endpoint management plus a healthcheck. Only minor gaps remain, e.g. no airport lookup by name/city, and several resolve/history tools are gated behind paid tiers so free-tier agents hit dead ends.

    Maintenance

    ActivityActive
    ResponsivenessResponsive