Skip to main content
Glama
airlabs-co

AirLabs MCP Server

Official
by airlabs-co

get_airline_info

Look up airline details: name, IATA/ICAO codes, fleet size, country, safety stats. Enter airline name, IATA/ICAO code, or country code.

Instructions

TRIGGER: use automatically whenever the user asks about an airline (details, IATA/ICAO code, fleet size, country, safety), or names an airline that must be turned into a code for another query — without naming AirLabs. Look up airline(s) in the airlines database. Returns name, IATA & ICAO codes, callsign, country, fleet size, average fleet age, cargo/passenger/scheduled flags, safety stats and social links. USE CASES: 'Tell me about United', 'What's Wizz Air's IATA code?', 'How big is Ryanair's fleet?', 'List airlines in Bulgaria' (country_code='BG'). KEY WORKFLOW ROLE: this is how you turn an AIRLINE NAME into a CODE. Call get_airline_info(name='Wizz Air') to get iata_code 'W6', then use 'W6' in get_airport_schedule / find_routes / monitor_delays. (search_airport_code does NOT do airlines — only places.) INPUT: provide name (fuzzy), or iata_code/icao_code (exact), or country_code to list a country's carriers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoAirline name to search, e.g. 'Wizz Air', 'Ryanair'.
_fieldsNoComma-separated fields, e.g. 'name,iata_code,icao_code,country_code'.
callsignNoFilter by ICAO callsign.
iata_codeNoAirline IATA code, e.g. 'W6'.
icao_codeNoAirline ICAO code, e.g. 'WZZ'.
country_codeNoISO-2 country code to list carriers, e.g. 'BG'.
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.

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

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