Skip to main content
Glama
airlabs-co

AirLabs MCP Server

Official
by airlabs-co

find_routes

Look up scheduled airline routes and days of operation between airports. Find which airlines fly a specific route and on which days.

Instructions

TRIGGER: use automatically whenever the user asks which airlines fly a route, whether a nonstop exists between two places, or on which days a route operates — without naming AirLabs. Look up the ROUTE timetable: which airlines operate a route and on which DAYS OF THE WEEK, with scheduled clock times (no live status). This is a planning/reference database, NOT real-time — use it for 'which airlines fly X to Y' and 'what days does this run', NOT for 'is it on time today'. USE CASES: 'Which airlines fly London to Tokyo?', 'What days does Wizz Air fly Sofia to London?', 'Does anyone fly nonstop A to B?'. INPUT: filter by dep_iata and/or arr_iata and/or airline_iata (resolve names to codes first). For 'soon/today with times', use get_airport_schedule instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax rows (up to 500; 50 for free keys).
_fieldsNoComma-separated fields to return.
arr_iataNoArrival airport IATA code, e.g. 'LTN'.
arr_icaoNoArrival airport ICAO code.
dep_iataNoDeparture airport IATA code, e.g. 'SOF'.
dep_icaoNoDeparture airport ICAO code.
flight_iataNoFilter by flight IATA number.
airline_iataNoFilter by airline IATA code, e.g. 'W6'.
airline_icaoNoFilter by airline ICAO code.
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.

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