Skip to main content
Glama

search_flights

Search for cheap flights across European low-cost airlines using flexible dates, multi-airport, and advanced filter options.

Instructions

Search for cheap flights on azair.eu across European low-cost airlines. Supports flexible date ranges, multiple airports per side, metro-area codes (e.g. MIL_ALL), anywhere (XXX), one-way or return, and all advanced filters (weekdays, time windows, stopover limits, overnight waits, transfers, Schengen-only).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
adultsNoNumber of adult travellers aged 12+ (default 1)
infantsNoNumber of infants under 2 years (default 0)
arr_dateYesLatest return date, format DD.MM.YYYY or YYYY-MM-DD
childrenNoNumber of children aged 2-11 (default 0)
currencyNoCurrency for prices, e.g. EUR, USD, GBP, PLN, CZK (default EUR)EUR
dep_dateYesEarliest departure date, format DD.MM.YYYY or YYYY-MM-DD
next_dayNoAllow waiting at the airport overnight so the next flight departs on the following day; 0 disallows overnight waits, up to 7 days (default 0)
same_arrNoRequire the return flight to depart from the same airport the outbound flight arrived at (default true)
same_depNoRequire the return flight to arrive at the same airport the outbound flight departed from (default true)
is_onewayNoSearch one-way flights only; false searches return flights (default false)
dst_airportYesDestination IATA code, e.g. STN, or XXX for anywhere in Europe
max_changesNoMaximum stopovers per flight leg, 0 means direct flights only (default 1)
src_airportYesSource airport IATA code, e.g. PRG, WMI, STN
dst_airportsNoAdditional destination airports searched together with dst_airport, e.g. LIN, BGY alongside MXP
src_airportsNoAdditional source airports searched together with src_airport, e.g. BRQ, NUE alongside PRG
max_days_stayNoMaximum trip length in nights between outbound and return flight (default 7)
max_hour_stayNoMaximum stopover (layover) duration between connecting flights as H:MM (default 23:20); applies only to itineraries with changes23:20
min_days_stayNoMinimum trip length in nights between outbound and return flight (default 2)
min_hour_stayNoMinimum stopover (layover) duration between connecting flights as H:MM (default 0:45); applies only to itineraries with changes0:45
schengen_onlyNoOnly allow transfers within the Schengen area (default false)
allow_transferNoAllow ground transfer between different airports during a connection, e.g. arriving at one airport and departing from another (default false)
dst_metro_codeNoDestination metro code covering all airports of a city, e.g. MIL_ALL, PAR_ALL, LON_ALL
src_metro_codeNoSource metro code covering all airports of a city, e.g. MIL_ALL (MXP, BGY, LIN), LON_ALL
return_weekdaysNoWeekdays the return flight may depart on, 0=Mon..6=Sun; omit for any day
max_hour_inboundNoLatest departure time of the return flight, 24h local time as H:MM (default 24:00)24:00
min_hour_inboundNoEarliest departure time of the return flight, 24h local time as H:MM (default 0:00)0:00
max_hour_outboundNoLatest departure time of the outbound flight, 24h local time as H:MM (default 24:00)24:00
min_hour_outboundNoEarliest departure time of the outbound flight, 24h local time as H:MM (default 0:00)0:00
departure_weekdaysNoWeekdays the outbound flight may depart on, 0=Mon, 1=Tue, 2=Wed, 3=Thu, 4=Fri, 5=Sat, 6=Sun; omit for any day
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden. It discloses that the tool searches azair.eu and is limited to European low-cost airlines, and it highlights advanced search capabilities. This adds meaningful behavioral context beyond the schema.

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 two sentences, front-loaded with the core purpose, and every word adds value. It efficiently summarizes the tool's scope without unnecessary detail.

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?

The tool has 29 parameters and no output schema, yet the description focuses mainly on search features. It does not explain the return format, error handling, or potential limitations beyond airline scope, leaving some gaps for such a complex 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?

The schema already covers 100% of parameters, so the baseline is 3. The description adds value by explaining special codes like 'MIL_ALL' and 'XXX' and summarizing filter categories (weekdays, time windows, stopover limits), which enriches parameter understanding.

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 what the tool does: 'Search for cheap flights on azair.eu across European low-cost airlines.' It uses specific verbs and resources, and its focus on flight search differentiates it from the sibling tool search_airports.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context by listing supported features like flexible date ranges, multiple airports, metro codes, anywhere (XXX), one-way or return, and advanced filters. It does not explicitly mention alternatives or exclusions, but the implied usage is clear for flight search scenarios.

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/yuriiter/azair-eu-mcp'

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