Skip to main content
Glama
smamidipaka6

Google Flights MCP Server

by smamidipaka6

get_general_flights_info

Retrieve comprehensive flight information for any route, including multiple flight options with details on prices, stops, and durations. Specify origin, destination, departure date, and preferences to get tailored results.

Instructions

Get general/comprehensive flight information for N 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.

    n_flights (int, optional): The number of flights to return. Defaults to 25.

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
n_flightsNo
Behavior3/5

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

No annotations provided, so description carries full burden. Details parameters and return format but does not disclose behavioral traits like rate limits, error handling, or authentication needs.

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?

Well-structured with clear intro, args list, and returns. Slightly verbose (e.g., 'general/comprehensive'), but information is effectively front-loaded.

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?

Covers all 10 parameters and return format with list of strings. Missing output schema and behavioral context like error messages or pagination, but adequate for a data-fetching tool.

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?

Schema has 0% description coverage; the description provides comprehensive, clear parameter explanations including format examples, defaults, and constraints (e.g., IATA codes, date format, seat types). This adds high value beyond 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 tool fetches general/comprehensive flight information with key parameters. Implicitly distinguishes from siblings by being general, but does not explicitly differentiate.

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 flights (making two calls), but lacks explicit when-to-use vs siblings like get_cheapest_flights or get_best_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