google-flights-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_airportA | |
| find_airports_nearA | |
| search_flightsA | |
| search_multi_cityC | |
| search_flexible_datesA | |
| compare_destinationsA | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a distinct purpose: airport resolution by name, airport search by location, standard flight search, multi-city flight search, flexible date search, and destination comparison. There is no overlap or ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., find_airport, search_flights, compare_destinations), making them predictable and easy to understand.
Six tools cover the essential flight search functionalities (airport lookup, single trip, multi-city, flexible dates, destination comparison) without being excessive or too few. The scope is well-defined.
The tool set covers all common flight search scenarios: single trip, multi-city, flexible dates, and destination comparison, along with airport resolution from names or coordinates. No obvious gaps for a search-only service.