All 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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_providersA | List flight inventory providers and whether each one is configured. |
| search_flightsB | Search all configured flight providers concurrently, normalize their offers, and deduplicate equivalent itineraries. |
| get_offer | Retrieve a previously returned normalized offer and all provider alternatives from the in-memory result cache. |
| search_date_rangeB | Search multiple outbound dates and stay lengths, returning the cheapest normalized offer for each date pair. |
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 3 tools
Each tool has a distinct purpose: listing providers, searching flights across providers, and searching across date ranges. No overlaps or ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case: list_providers, search_flights, search_date_range. No deviations.
Three tools is well-scoped for a flight search server, covering configuration listing, general search, and date-range search without excess or deficiency.
The set covers core flight search functionality, but lacks filters (e.g., by airline, price) or provider-specific queries. Minor gap but sufficient for the stated purpose.