AirLabs MCP Server

Official

by airlabs-co

Overview Schema Related Servers Score Discussions

JavaScript

Remote

Server Quality Checklist

Profile completionA complete profile improves this server's visibility in search results.

Latest release: v1.0.0
Disambiguation5/5
Each tool has a clearly distinct purpose: airport code search, live schedules, airline info, aircraft lookup, delay monitoring, route timetables, etc. Descriptions preemptively clarify overlaps (e.g., get_airport_schedule vs. find_routes vs. monitor_delays), ensuring agents can reliably select the correct tool.
Naming Consistency3/5
Tool names mix patterns: get_ prefixed info tools (get_airline_info), find_ verbs (find_routes), lookup_, monitor_, search_, track_. While all are descriptive, the lack of a single consistent convention (e.g., verb_noun) adds slight ambiguity, especially between get_airport_schedule and get_flight_status.
Tool Count5/5
With 12 tools, the set is well-scoped for an aviation data server. Each tool addresses a distinct core function (resolving codes, live flight data, aircraft details, delays, routes) without redundancy or bloat. The count feels appropriate for the domain's complexity.
Completeness5/5
The tool set covers a comprehensive range of aviation information needs: airport/airline details, code resolution, live schedules, route planning, delay monitoring, flight status, aircraft lookup, and live tracking. No obvious gaps exist—the surface enables agents to answer most common queries about flights, airports, airlines, and aircraft.
Average 4.6/5 across 12 of 12 tools scored. Lowest: 3.9/5.
See the Tool Scores section below for per-tool breakdowns.
- No community issues in the last 6 months
- 6 commits in the last 12 weeks
- No stable releases found
- No critical vulnerability alerts
- No high-severity vulnerability alerts
- No code scanning findings
- CI status not available
This repository is licensed under MIT License.
This repository includes a README.md file.
No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.
Tip: use the "Try in Browser" feature on the server page to seed initial usage.
Add a glama.json file to provide metadata about your server.
If you are the author, simply .
If the server belongs to an organization, first add glama.json to the root of your repository:
```
{
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}
```
Then . Browse examples.
Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must fully disclose behavior. It states the tool returns ISO-2/ISO-3 codes, name, continent, and currency, which is helpful. However, it does not clarify what happens when both parameters are omitted (e.g., returns all countries?), nor does it address edge cases or errors. The description also introduces ambiguity by saying 'resolve a country NAME' while the schema only has a 'code' parameter for ISO-2 codes, potentially misleading about input.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise at two sentences plus a use case. It is front-loaded with a clear trigger statement. However, the slight contradiction between 'name' and 'code' introduces unnecessary noise. Overall, it is efficient but not perfectly clear.
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 tool's simplicity (2 optional params, no output schema), the description covers the main purpose and return fields. However, it fails to address the input ambiguity (name vs. code) and does not specify behavior when both parameters are missing. While the return format is described, the lack of clarity on inputs reduces completeness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema provides 100% coverage for both parameters ('code' and '_fields'). The description adds confusion by stating the tool resolves a country NAME, but the 'code' parameter is an ISO-2 code, not a name. This mismatch misleads about valid inputs. The description reiterates return fields but does not clarify the ambiguity or add meaningful detail beyond the schema.
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: to resolve a country name to its ISO-2 code for filtering airlines/airports. It specifies the resource (countries database) and the verb (look up). It also distinguishes itself from sibling tools by emphasizing its role as a helper for filtering, not for general facts.
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 explicitly instructs when to use the tool ('TRIGGER: use mainly as a helper to resolve a country NAME to its ISO-2 code for filtering airlines/airports') and when not to use it ('not for general country facts'). It provides concrete use cases, such as determining country codes for Bulgaria or Spain, and explains how it assists with filtering by country_code.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must bear the burden. It describes return types (matched airports, cities, countries, airports-by-city/country). It is a read-only search operation, clearly safe. No mention of rate limits or pagination, but acceptable for a simple lookup.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is front-loaded with trigger conditions and key information. It is somewhat lengthy but each sentence adds value (triggers, use cases, exclusions). Could be slightly more concise, but structure is logical.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity and the excellent schema and sibling list, the description covers purpose, usage context, limitations, and provides examples. No output schema, but return types are described. Completely adequate for correct selection and invocation.
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 coverage is 100% (all 3 parameters documented). The description adds context for 'q' (part of name, length), but schema already describes it. No significant additional meaning beyond schema, so baseline 3 is appropriate.
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 resolves place names into IATA/ICAO codes, with examples. It distinctly separates from siblings by explicitly noting it does not resolve airline names, directing to get_airline_info instead.
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?
Explicit TRIGGER language: 'use automatically (often as the FIRST step)', specific use cases (e.g., 'What's the code for Sofia?'), and clear guidance on when not to use (airline names) with alternative tool named.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It discloses positional/map data nature, and that unfiltered returns very large global list. Missing data freshness, rate limits, or auth requirements, but core behavior is well-covered.
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?
Well-structured with trigger, description, use cases, and input guidance. Every sentence adds value, no wasted words. Appropriate length for a complex tool.
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 11 parameters with full schema coverage and no output schema, description explains purpose, usage, and distinguishes from siblings. Could explicitly mention return field names, but the description already lists them in the first sentence.
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%, baseline 3. Description lists filter options but does not add meaning beyond schema descriptions. It reinforces the need for filtering but doesn't provide additional semantics.
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?
Description clearly states it returns live aircraft positions (lat, lng, altitude, speed, heading, squawk). Includes specific use cases and distinguishes from schedule tools like get_airport_schedule and get_flight_status.
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?
Explicitly tells when to use automatically ('whenever the user asks where aircraft are flying right now'), provides concrete use cases, and advises against using for schedules by naming alternatives. Also warns to always filter or pass a bbox.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It explains sorting by distance, default distance, and inclusion of nearby cities. Does not mention return format or API limitations, but for a read-only query tool this is sufficient.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loaded with a bold 'TRIGGER' instruction, then concise details. Every sentence adds value. Slightly verbose but efficient and well-organized.
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?
Covers trigger, input requirements, usage relative to sibling tools, and mentions output order (sorted by distance). Lacks explicit return structure but acceptable for a straightforward query tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema has 100% parameter descriptions. The description adds value by clarifying that 'distance' is in km and defaults to 50, and advises using search_airport_code to resolve place names to coordinates. Does not explicitly describe 'lang' but that is fully covered in schema.
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 it finds nearest airports to a coordinate, sorted by distance. It distinguishes from siblings like search_airport_code by specifying coordinate input and automatic trigger for 'closest airport' queries.
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?
Explicitly instructs to use automatically when user asks for nearest airport, provides use cases, and advises to use search_airport_code first if user names a place instead of coordinates. Also specifies fallback for airport code requests.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Describes parameter behavior (name fuzzy, iata_code/icao_code exact, country_code lists carriers). Mentions returned fields comprehensively. No annotations provided, so description carries full burden; could clarify fuzzy matching behavior for multiple matches, but overall transparent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
While lengthy (multiple paragraphs), it is well-structured into clear sections (TRIGGER, USE CASES, KEY WORKFLOW ROLE, INPUT). Each sentence adds value. Front-loaded with trigger instruction. Could be slightly more concise but structure aids readability.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Complete for a lookup tool without output schema: explains what is returned (name, codes, callsign, country, fleet, safety stats, social links), parameter effects, and integration with workflow. Covers use cases and alternatives thoroughly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% (baseline 3). Description adds value beyond schema by explaining fuzzy vs exact matching, country_code listing carriers, and special parameter behaviors. Joins parameter semantics with workflow context.
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?
Description clearly states it looks up airline(s) in the airlines database, returning name, codes, and other details. It distinguishes from siblings like search_airport_code, which does not do airlines. Use cases are explicit.
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?
Includes a 'TRIGGER' section for automatic use, 'USE CASES' with examples, and a 'KEY WORKFLOW ROLE' explaining how to turn an airline name into a code for other queries. Explicitly mentions alternative tool (search_airport_code) and when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description fully takes on the burden of transparency. It describes inputs (iata_code, icao_code, country_code, city_code), the output fields (full name, city, country, coordinates, elevation, timezone, runways, yearly departures, localized names), and a trigger for automatic use. However, it does not address potential limitations like the maximum number of airports returned for country/city queries or error handling.
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 well-structured with clear sections: TRIGGER, main function, USE CASES, WORKFLOW ROLE, INPUT. It is front-loaded with the most important trigger information and every sentence adds value. No redundancy or fluff.
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?
The description covers triggers, use cases, workflow integration, input options, and output fields comprehensively. Absence of output schema is mitigated by listing output fields. Minor missing detail: whether country/city queries have a result limit, but overall very complete for a lookup tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so baseline is 3. The description adds contextual value by linking parameters to use cases (e.g., iata_code for a single airport, country_code for a list) and explaining the _fields parameter. This goes beyond the schema's individual parameter 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 looks up airport details by code and returns comprehensive information. The TRIGGER statement instructs automatic use when a user asks about an airport's details or expands a code, distinguishing it from siblings by specifying its role after other tools like get_airport_schedule.
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?
Explicit use cases are provided (e.g., 'What's the full name of LHR?', 'List all airports in Bulgaria') along with a workflow role that tells the agent to call this tool after get_airport_schedule or find_routes to convert codes to names. This gives clear direction on when and how to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, but description reveals key behavior: returns only single closest live/scheduled/landed instance, non-destructive read operation. Could mention rate limits, but not required.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Structured with TRIGGER, INPUT, NOTE blocks for readability. Slightly lengthy but each sentence adds unique value. Front-loaded with trigger conditions.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given 3 parameters and no output schema, the description fully covers return fields, single-instance behavior, alternative tool reference, and a prerequisite step. No gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, but description adds value by explaining the alternative parameters (flight_iata vs flight_icao) with example formats, and the _fields parameter for response trimming.
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 'Get the live status of ONE flight by its flight number' and lists return fields, distinguishing it from siblings like get_airport_schedule which returns multiple instances.
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?
Explicitly defines TRIGGER for automatic use, provides example use cases, and states when NOT to use this tool (use get_airport_schedule for daily instances). Also gives a prerequisite step for airline name conversion.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses key behavioral details: position data is only included when querying a specific aircraft, limit cap (500 max, 50 for free keys), and the range of return fields. However, since there are no annotations, it could mention that this is a read-only operation and any potential freshness of data. The lack of contradiction and the added context elevate it above average.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description starts with a clear trigger statement and is well-organized with use cases and input guidance. While it is somewhat verbose, every sentence serves a purpose. It could be tightened slightly, but the structure aids readability and comprehension.
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 8 parameters and no output schema, the description adequately covers how to use the tool for both specific aircraft and fleet queries, lists return fields, and addresses a common ambiguity (airline name vs. code). Without an output schema, it doesn't detail the exact response format, but the listed fields and behavioral notes make it functional for the agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description adds significant meaning beyond the schema: it groups parameters (reg_number/hex/msn for specific aircraft vs. airline codes for fleet listing), clarifies the position inclusion condition, and advises on resolving airline names. This context is crucial for correct use and goes well beyond the baseline 3 given 100% schema coverage.
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 looks up aircraft in a fleets database and lists the specific fields returned (type, model, manufacturer, etc.). It distinguishes from sibling tools by specifying its domain (aircraft lookup vs. airports/routes/flights) and providing a trigger for automatic invocation when the user asks about a specific aircraft or airline fleet.
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 explicitly says when to use (user asks about aircraft or airline fleet) and when not to (resolving airline name via get_airline_info first). It provides concrete use cases with examples, and explains the different input modes (specific aircraft vs. fleet listing). This gives the agent clear decision criteria.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, but description discloses return fields (name, code, country, coordinates, timezone, population/popularity), indicates read-only intent (no mutation mentioned), and provides use case examples. Could be improved by explicitly stating read-only.
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?
Description is front-loaded with trigger, then action, returns, use cases, and sibling differentiation. Every sentence adds value with no fluff.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple lookup tool with 3 optional parameters and no output schema, the description covers all essential context: when to use, what it returns, example inputs, and differentiation from related tools.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
All parameters have schema descriptions (100% coverage), but description adds value by specifying default return fields when `_fields` is omitted, giving example values for `city_code` ('LON') and `country_code` ('BG'), and clarifying the aviation context.
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?
Description clearly states the tool looks up cities by code or country in an aviation database, with verb 'look up', resource 'cities in the world cities database', and distinguishes from sibling 'search_airport_code' which converts city name to code.
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?
Explicitly states when to use: aviation city code/grouping queries or listing cities of a country in aviation context; when not to use: general geography; provides alternative sibling tool for name-to-code conversion.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description fully discloses it is a planning/reference database with no live status, and lists what it returns (airlines, days, scheduled times). This is complete transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is thorough but not wasteful: a trigger statement, core functionality, use cases, and input tips. It is slightly long but well-structured and front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given 9 parameters, no annotations, and no output schema, the description covers purpose, usage guidelines, filtering hints, and exclusions completely. Missing output description is acceptable as no output schema exists.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% so baseline is 3. The description adds value by explaining the filtering fields (dep_iata, arr_iata, airline_iata) and instructs to resolve names to codes first, providing context beyond the schema.
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 looks up route timetables: which airlines operate a route and on which days, with scheduled times. It distinguishes from real-time tools and provides specific use cases like 'Which airlines fly London to Tokyo?'.
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?
Explicitly says when to use (user asks about airlines flying a route, nonstop existence, days of operation) and when NOT to use (not for real-time status, directs to get_airport_schedule for 'soon/today with times'). Also advises to resolve names to codes first.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, description fully discloses behavioral traits: time window covers recent past to hours ahead, explains status meanings (scheduled, active, landed), and gives specific filtering guidance. Warns not to silently hide rows and how to handle ambiguous queries.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Description is well-structured with sections (TRIGGER, USE CASES, INPUT, WORKFLOW, TIME WINDOW). Though lengthy, each section serves a purpose. Slightly verbose in places but overall efficient for the complexity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema, description adequately explains return fields and statuses. Covers time window, filtering, and edge cases. Complete for the tool's purpose and context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Input schema has 100% coverage with descriptions for all 10 parameters. Description adds value by clarifying usage of dep_iata/arr_iata as main input, optional airline_iata and flight_iata, and explains limit max values per key type. This exceeds the baseline.
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?
Description clearly states the tool retrieves live departures/arrivals board for an airport, specifying fields like dep_time, arr_time, status, etc. It distinguishes from siblings by explicitly noting that find_routes returns weekly timetable without live times.
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?
Provides explicit trigger conditions (when user asks about flights 'today/now/soon'), use cases, and a workflow example. Clearly states when NOT to use this tool (do not use find_routes for soon/today) and gives alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It discloses that delayed flights are often already airborne (active status) rather than scheduled, explains this is correct data, and gives guidance on how to handle user preference—demonstrating full transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is long but efficiently front-loaded with trigger instruction, followed by purpose, use cases, parameter guidance, and status note. Every sentence adds value; minor redundancy could be trimmed but overall well-structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has 6 parameters (1 required), no output schema, and complex behavioral nuances, the description covers all necessary aspects: trigger, use cases, parameter usage, name resolution, and data interpretation. It explains the return format (delay minutes, new estimated time).
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with descriptions, so baseline is 3. The description adds value by providing example values for 'delay', clarifying the resolution of names for airline/airport parameters, and explaining the 'type' parameter scope. Enriches beyond schema.
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 lists flights delayed beyond a threshold with optional filters, and includes trigger instructions and use cases that differentiate it from siblings like get_airport_schedule or track_live_flights.
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?
Explicit trigger instruction: 'use automatically whenever the user asks about delayed flights' with specific query patterns. Also directs to resolve airport/airline names first using other tools, and advises on status filtering based on user intent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

Confirm that the MCP server is working as expected.
Confirm that there are no obvious security issues.
Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

Copy to your README.md:

[![airlabs-mcp MCP server](https://glama.ai/mcp/servers/airlabs-co/airlabs-mcp/badges/card.svg)](https://glama.ai/mcp/servers/airlabs-co/airlabs-mcp)

Score Badge

Copy to your README.md:

[![airlabs-mcp MCP server](https://glama.ai/mcp/servers/airlabs-co/airlabs-mcp/badges/score.svg)](https://glama.ai/mcp/servers/airlabs-co/airlabs-mcp)

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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/airlabs-co/airlabs-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server