Skip to main content
Glama

Search Flights (Aviasales)

aviasales.flights.search
Read-onlyIdempotent

Search for flights between airports using IATA codes, with optional filters for destination, date, direct flights, and currency.

Instructions

Search for flights between airports

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
originYesDeparture city or airport IATA code (e.g. MOW, JFK, BKK)
destinationNoArrival IATA code (omit to search all destinations)
departure_dateNoDeparture date in YYYY-MM-DD format (filters results to this date and later)
direct_onlyNoOnly show non-stop flights (default false)
currencyNoCurrency code for prices (default usd)
limitNoMax number of results to return (default 10)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoTool response payload. Shape varies per tool — consult the tool description and inputSchema. May be an object, array, string, or number depending on the upstream provider response.
errorNoPresent only when the call failed. Includes error code, message, request_id, and any provider-specific extras.
Behavior2/5

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

Description adds no behavioral traits beyond the annotations, which already indicate read-only, idempotent, and open-world semantics. No mention of pagination, rate limits, or response details.

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?

Single sentence, no wasted words. However, it could be slightly expanded to include key constraints (e.g., required origin) without losing conciseness.

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?

Output schema exists, so return values are covered by schema. Description is minimal but sufficient given 100% parameter coverage. Could mention that origin is required and destination is optional.

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%, so the baseline is 3. The description does not add any additional meaning to the parameters beyond what is in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states 'Search for flights between airports'. The verb 'Search' and resource 'flights' are specific. It distinguishes from sibling tools like 'aviasales.flights.calendar' and 'aviasales.flights.cheap' by being the general search tool.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus siblings like 'aviasales.flights.cheap' or 'aviasales.flights.calendar'. The description does not mention appropriateness contexts or alternatives.

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/whiteknightonhorse/APIbase'

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