Variflight MCP Server
OfficialServer 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchFlightsByDepArrA | Search for flights between airports or cities by date. For cities with multiple airports, use depcity and arrcity parameters; otherwise use dep and arr parameters. Date must be in YYYY-MM-DD format. For today's date, use the getTodayDate tool. All airport/city codes must be valid IATA 3-letter codes (e.g.BJS for city of Beijing, PEK for Beijing Capital Airport). |
| searchFlightsByNumberA | Search flights by flight number and date. Flight number should include airline code (e.g. MU2157, CZ3969). dep and arr are optional, keep empty if you don't know them. Date format: YYYY-MM-DD. IMPORTANT: For today's date, you MUST use getTodayDate tool instead of hardcoding any date. Airport codes (optional) should be IATA 3-letter codes. |
| getFlightTransferInfoB | Get flight transfer info by departure city and arrival city and departure date. Date format: YYYY-MM-DD. IMPORTANT: For today's date, you MUST use getTodayDate tool instead of hardcoding any date. Airport codes should be IATA 3-letter codes. |
| flightHappinessIndexC | using this tool when you need information related to following topics: Detailed flight comparisons (punctuality, amenities, cabin specs),Health safety protocols for air travel,Baggage allowance verification,Environmental impact assessments,Aircraft configuration visualization,Comfort-focused trip planning (seat dimensions, entertainment, food). etc. |
| getRealtimeLocationByAnumA | Get flight realtime location by aircraft number. aircraft number should be Aircraft registration numberlike B2021, B2022, B2023, etc. if aircraft number is unknown, you shuold try to request it using searchFlightsByNumber tool |
| getTodayDateA | Get today's date in local timezone (YYYY-MM-DD format). Use this tool whenever you need today's date - NEVER hardcode dates. |
| getFutureWeatherByAirportA | Get airport future weather for 3days (today、tomorrow、the day after tomorrow) by airport IATA 3-letter code. Airport codes should be IATA 3-letter codes (e.g. PEK for Beijing, SHA for Shanghai, CAN for Guangzhou, HFE for Hefei). |
| searchFlightItinerariesB | Search for purchasable flight options and the lowest price using the departure city three-letter code, arrival city three-letter code, and departure date. (e.g. BJS for Beijing, SHA for Shanghai, CAN for Guangzhou, HFE for Hefei). |
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 8 tools
There is significant overlap between searchFlightItineraries, searchFlightsByDepArr, and getFlightTransferInfo, all involving flight search between locations with date parameters. However, descriptions clarify some distinctions: searchFlightItineraries focuses on purchasable options and pricing, searchFlightsByDepArr handles airport/city flexibility, and getFlightTransferInfo specifically targets transfer information. The flightHappinessIndex stands out as distinct, covering comfort and amenities rather than routing.
Naming is inconsistent with mixed conventions: flightHappinessIndex uses camelCase, while all other tools use snake_case (e.g., getFlightTransferInfo, searchFlightsByDepArr). Verb patterns vary: 'get' (getFlightTransferInfo, getFutureWeatherByAirport, getRealtimeLocationByAnum, getTodayDate) vs. 'search' (searchFlightItineraries, searchFlightsByDepArr, searchFlightsByNumber), with flightHappinessIndex lacking a clear verb. This inconsistency reduces predictability.
With 8 tools, the count is reasonable for a flight information server, covering key aspects like search, transfers, weather, location, and comfort. It's slightly on the higher side but well-scoped, as each tool addresses a specific need without obvious bloat. The domain of flight data supports this number, ensuring agents have necessary operations without being overwhelmed.
The tool set provides good coverage for flight-related queries, including search (by itinerary, departure/arrival, number), transfer info, real-time location, weather, and comfort assessments. Minor gaps exist, such as lack of tools for booking management, flight status updates beyond location, or historical data, but core workflows for information retrieval are well-covered, allowing agents to handle most common requests effectively.