Skip to main content
Glama
HaroldLeo

Google Flights MCP Server

by HaroldLeo

search_one_way_flights

Find available one-way flights for a specific date between two airports, with options to filter by passenger count, cabin class, and retrieve only the cheapest option.

Instructions

Fetches available one-way flights for a specific date between two airports.
Can optionally return only the cheapest flight found.

Args:
    origin: Origin airport code (e.g., "DEN").
    destination: Destination airport code (e.g., "LAX").
    date: The specific date to search (YYYY-MM-DD format).
    adults: Number of adult passengers (default: 1).
    children: Number of children (2-11 years, default: 0).
    infants_in_seat: Number of infants in seat (under 2 years, default: 0).
    infants_on_lap: Number of infants on lap (under 2 years, default: 0).
    seat_type: Fare class - economy/premium_economy/business/first (default: "economy").
    return_cheapest_only: If True, returns only the cheapest flight (default: False).

Example Args:
    {"origin": "SFO", "destination": "JFK", "date": "2025-07-20"}
    {"origin": "SFO", "destination": "JFK", "date": "2025-07-20", "adults": 2, "children": 1}
    {"origin": "SFO", "destination": "JFK", "date": "2025-07-20", "return_cheapest_only": true}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
originYes
destinationYes
dateYes
adultsNo
childrenNo
infants_in_seatNo
infants_on_lapNo
seat_typeNoeconomy
return_cheapest_onlyNo
max_resultsNo
compact_modeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions the tool 'fetches available one-way flights' and can 'optionally return only the cheapest flight,' which covers basic behavior. However, it lacks details on rate limits, error handling, authentication needs, response format, or what happens with no results. For an 11-parameter tool with no annotations, this is a significant gap in behavioral disclosure.

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 appropriately sized and well-structured, with a clear opening sentence stating the purpose, followed by a detailed 'Args' section and example usage. Every sentence adds value, though the example section could be slightly more concise. It's front-loaded with the core functionality.

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 the complexity (11 parameters, no annotations, but with an output schema), the description is mostly complete. It thoroughly documents parameters and provides usage examples. Since an output schema exists, the description doesn't need to explain return values. However, it could improve by adding more behavioral context, such as error handling or performance expectations.

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?

The description adds substantial meaning beyond the input schema, which has 0% schema description coverage. It provides clear explanations for all parameters listed in the 'Args' section (e.g., 'Origin airport code (e.g., "DEN")', 'Number of adult passengers (default: 1)'), including examples and default values. This fully compensates for the lack of schema descriptions, making parameters well-understood.

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 specific action ('fetches available one-way flights') and resource ('for a specific date between two airports'), with the optional behavior of returning only the cheapest flight. It distinguishes from siblings by focusing on one-way flights specifically, unlike round-trip or multi-city tools in the sibling list.

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 implies usage context through the tool name and description, suggesting it should be used for one-way flight searches. However, it doesn't explicitly state when to use this tool versus alternatives like 'search_round_trip_flights' or 'search_direct_flights' from the sibling list, nor does it mention any prerequisites or exclusions.

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/HaroldLeo/google-flights-mcp'

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