flight
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SERPAPI_API_KEY | Yes | Your SerpApi API key |
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 |
|---|---|
| search_flightsA | Search for flights using Google Flights via SerpApi. Args: departure_id: 3-letter departure airport code (e.g. AUS) arrival_id: 3-letter arrival airport code (e.g. JFK) outbound_date: departure date in YYYY-MM-DD format return_date: return date in YYYY-MM-DD format (omit for one-way) currency: currency code, defaults to USD |
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 1 tool
With only a single tool, there is no ambiguity whatsoever. The tool's purpose is clearly distinct by virtue of being the only one.
The single tool name 'search_flights' follows a clear verb_noun convention, and consistency is trivially satisfied with just one name.
Having only one tool for a flight-related server is too few. While the search functionality is useful, a typical flight service would expect additional operations like booking, cancellation, or flight status, making this feel extremely minimal for the apparent domain.
The tool surface is severely incomplete for the flight domain—it only covers searching. There are no tools for selecting, booking, modifying, or canceling flights, which are obvious core operations, leading to significant gaps that would cause agent failures in real workflows.