Skip to main content
Glama
smamidipaka6

Google Flights MCP Server

by smamidipaka6
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

get_cheapest_flights

Find the cheapest flight options between two airports on a specific date. Supports one-way and round-trip searches with seat and passenger preferences.

Instructions

Get the cheapest flight information for a given origin, destination, and departure date. If the user wants to do a round-trip, you will need to make two one-way trip calls.

Args:
    origin (str): The origin airport IATA code (ex: "ATL", "SCL", "JFK").
    destination (str): The destination airport IATA code (ex: "DTW", "ICN", "LIR").
    departure_date (str): The departure date in YYYY-MM-DD format.

    trip_type (str, optional): The type of trip ("one-way" or "round-trip" only). Defaults to "one-way".
    seat (str, optional): The type of seat ("economy", "premium-economy", "business", or "first" only). Defaults to "economy".
    adults (int, optional): The number of adults. Defaults to 1.
    children (int, optional): The number of children. Defaults to 0.
    infants_in_seat (int, optional): The number of infants in a seat. Defaults to 0.
    infants_lap (int, optional): The number of infants on a lap. Defaults to 0.

Returns:
    list[str]: A list of flight information strings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
originYes
destinationYes
departure_dateYes
trip_typeNoone-way
seatNoeconomy
adultsNo
childrenNo
infants_in_seatNo
infants_on_lapNo

Tool Definition Quality

A3.6/5.0
Behavior3/5

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

The description explains the return format (list of flight info strings) and parameter behavior, but lacks disclosure of side effects, permissions, or rate limits. Since no annotations are provided, the description carries full burden and is adequate but not fully 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?

The description is well-structured with an Args/Returns format, but is somewhat lengthy. The round-trip note is useful and front-loaded. Overall, it is organized and clear.

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 9 parameters, no output schema, and no annotations, the description covers all parameters with examples and defaults, and describes the return type. It is complete for the complexity of the 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 description provides detailed parameter explanations with examples (e.g., origin: 'ATL'), default values, and allowed values for trip_type, seat, etc. This adds significant value beyond the input schema, which has 0% description coverage.

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?

The description clearly states it retrieves cheapest flight information for a given origin, destination, and departure date. The purpose is specific and distinct from sibling tools like 'get_best_flights' or 'get_general_flights_info', though it does not explicitly differentiate itself.

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

Usage Guidelines3/5

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

The description provides a usage guideline for round-trip requests (making two one-way calls), but does not include when to use this tool versus alternatives like 'get_best_flights' or 'get_time_filtered_flights'. It implies one-way is the default.

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/smamidipaka6/flights-mcp-server'

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