Skip to main content
Glama
smamidipaka6

Google Flights MCP Server

by smamidipaka6
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

get_best_flights

Get the best flight options from Google Flights by specifying origin, destination, departure date, and optional trip type, seat class, and passenger details.

Instructions

Get the best flights as determined by Google Flights 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
Behavior2/5

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

No annotations present, so description carries full burden. Does not disclose safety, error handling, rate limits, or return format details beyond 'list of flight information strings'. Minimal transparency for a flight search tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Structured with sections but somewhat verbose, repeating 'optional' and using docstring style. Could be more succinct while retaining clarity.

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?

Covers parameters well but lacks broader context: no explanation of 'best flights' criteria, no mention of error scenarios, and no details on return content beyond string list. Adequate but leaves gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Provides detailed parameter documentation with examples, defaults, and allowed values (e.g., IATA codes, date format, seat types). Compensates fully for 0% schema coverage, giving significant meaning beyond simple titles.

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?

Clearly states it retrieves best flights from Google Flights for given origin, destination, departure date. Explicitly distinguishes from siblings by mentioning round-trip requires two calls, differentiating from get_cheapest_flights and get_general_flights_info.

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?

Provides guidance for round-trip (make two one-way calls) but does not explicitly state when to use this tool versus siblings. No mention of when to prefer get_cheapest_flights or get_time_filtered_flights.

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