flightHappinessIndexUse this tool when the user wants comfort-focused details for a known flight, such as punctuality, aircraft type, cabin configuration, seat comfort, meals, entertainment, or other onboard experience details. This tool works best when a specific flight number and date are already known. Do not use it for fare search, itinerary recommendation, or raw price comparison.Input schema{
"type": "object",
"properties": {
"fnum": {
"type": "string",
"pattern": "^[A-Z0-9]{2,3}[0-9]{1,4}$",
"description": "Flight number including airline code (e.g. MU2157, CZ3969)"
},
"date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Flight date in YYYY-MM-DD format. IMPORTANT: If the user input contains only month and day, use getTodayDate to determine the year. For today's date, use getTodayDate instead of hardcoding."
},
"dep": {
"type": "string",
"minLength": 3,
"maxLength": 3,
"pattern": "^[A-Z]{3}$",
"description": "Departure airport IATA 3-letter code (e.g. HFE for Hefei)"
},
"arr": {
"type": "string",
"minLength": 3,
"maxLength": 3,
"pattern": "^[A-Z]{3}$",
"description": "Arrival airport IATA 3-letter code (e.g. CAN for Guangzhou)"
}
},
"required": [
"fnum",
"date"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
} | — | | — |
getFlightPriceByCitiesUse this tool when the user needs structured raw pricing data. It returns sale flights between two cities as a list of flights, and each flight contains cabin entries with prices. This is better than searchFlightItineraries when the caller needs per-flight, per-cabin price details instead of a natural-language recommendation summary. All city codes must be valid IATA 3-letter codes (e.g. BJS for Beijing, SHA for Shanghai, CAN for Guangzhou, HFE for Hefei).Input schema{
"type": "object",
"properties": {
"dep_city": {
"type": "string",
"pattern": "^[A-Z]{3}$",
"description": "Departure city 3-letter code (e.g. BJS for Beijing, SHA for Shanghai, CAN for Guangzhou, HFE for Hefei)"
},
"arr_city": {
"type": "string",
"pattern": "^[A-Z]{3}$",
"description": "Arrival city 3-letter code (e.g. BJS for Beijing, SHA for Shanghai, CAN for Guangzhou, HFE for Hefei)"
},
"dep_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Departure date in YYYY-MM-DD format, for example 2026-04-20. IMPORTANT: If the user input contains only month and day, use getTodayDate to determine the year. For today's date, use getTodayDate instead of hardcoding."
}
},
"required": [
"dep_city",
"arr_city",
"dep_date"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
} | — | | — |
getFlightTransferInfoSearch connecting flight options between a departure city and an arrival city on a specific date. Use city IATA 3-letter codes such as BJS, SHA, or LAX. This tool is for transfer or connection itineraries between cities, not for airport weather, airport facilities, or realtime tracking. Date must be in YYYY-MM-DD format. For today's date, use getTodayDate instead of hardcoding.Input schema{
"type": "object",
"properties": {
"depdate": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Departure date in YYYY-MM-DD format. IMPORTANT: If the user input contains only month and day, use getTodayDate to determine the year. For today's date, use getTodayDate instead of hardcoding."
},
"depcity": {
"type": "string",
"minLength": 3,
"maxLength": 3,
"pattern": "^[A-Z]{3}$",
"description": "Departure city IATA 3-letter code (e.g. BJS for Beijing, CAN for Guangzhou)"
},
"arrcity": {
"type": "string",
"minLength": 3,
"maxLength": 3,
"pattern": "^[A-Z]{3}$",
"description": "Arrival city IATA 3-letter code (e.g. SHA for Shanghai, LAX for Los Angeles)"
}
},
"required": [
"depdate",
"depcity",
"arrcity"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
} | — | | — |
getFutureWeatherByAirportGet the 3-day airport weather forecast for today, tomorrow, and the day after tomorrow by airport IATA 3-letter code, such as PEK, SHA, CAN, or HFE.Input schema{
"type": "object",
"properties": {
"airport": {
"type": "string",
"pattern": "^[A-Z]{3}$",
"description": "Airport IATA 3-letter code (e.g. PEK for Beijing, SHA for Shanghai, CAN for Guangzhou, HFE for Hefei)"
}
},
"required": [
"airport"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
} | — | | — |
getRealtimeLocationByAnumGet realtime flight location by aircraft registration number, also called tail number, such as B2021 or B2022. Use this only when the aircraft registration number is known. If the registration number is unknown, first try to find the flight through searchFlightsByNumber and then use the aircraft registration number from that result.Input schema{
"type": "object",
"properties": {
"anum": {
"type": "string",
"description": "Aircraft registration number, also called tail number, such as B2021, B2022, or B2023."
}
},
"required": [
"anum"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
} | — | | — |
getTodayDateGet today's date in local timezone (YYYY-MM-DD format). Use this tool whenever you need today's date - NEVER hardcode dates.Input schema{
"type": "object",
"properties": {
"random_string": {
"type": "string",
"description": "Optional placeholder parameter. Normally omit it."
}
},
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
} | — | | — |
searchFlightItinerariesUse this tool when the user wants a concise recommended itinerary summary in natural language. It returns a text-style result that summarizes how many sale flights match, the overall lowest price, the shortest duration, and several recommended options. Use city IATA 3-letter codes only. If the user instead needs structured raw flight pricing data with each flight and cabin price, use getFlightPriceByCities.Input schema{
"type": "object",
"properties": {
"depCityCode": {
"type": "string",
"pattern": "^[A-Z]{3}$",
"description": "Departure city 3-letter code (e.g. BJS for Beijing, SHA for Shanghai, CAN for Guangzhou, HFE for Hefei)"
},
"depDate": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Departure date in YYYY-MM-DD format, for example 2025-07-04. IMPORTANT: If the user input contains only month and day, use getTodayDate to determine the year. For today's date, use getTodayDate instead of hardcoding."
},
"arrCityCode": {
"type": "string",
"pattern": "^[A-Z]{3}$",
"description": "Arrival city 3-letter code (e.g. BJS for Beijing, SHA for Shanghai, CAN for Guangzhou, HFE for Hefei)"
}
},
"required": [
"depCityCode",
"depDate",
"arrCityCode"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
} | — | | — |
searchFlightsByDepArrSearch direct flights by departure and arrival location plus date. Use depcity and arrcity when the user specifies cities such as BJS or SHA. Use dep and arr when the user specifies exact airports such as PEK or PVG. Provide one departure field and one arrival field, and do not mix city and airport codes for the same side. All codes must be valid IATA 3-letter codes. Date must be in YYYY-MM-DD format. For today's date, use getTodayDate instead of hardcoding.Input schema{
"type": "object",
"properties": {
"dep": {
"type": "string",
"minLength": 3,
"maxLength": 3,
"pattern": "^[A-Z]{3}$",
"description": "Departure airport IATA 3-letter code (e.g. PEK for Beijing, CAN for Guangzhou)"
},
"depcity": {
"type": "string",
"minLength": 3,
"maxLength": 3,
"pattern": "^[A-Z]{3}$",
"description": "Departure city IATA 3-letter code (e.g. BJS for Beijing, CAN for Guangzhou)"
},
"arr": {
"type": "string",
"minLength": 3,
"maxLength": 3,
"pattern": "^[A-Z]{3}$",
"description": "Arrival airport IATA 3-letter code (e.g. SHA for Shanghai, HFE for Hefei)"
},
"arrcity": {
"type": "string",
"minLength": 3,
"maxLength": 3,
"pattern": "^[A-Z]{3}$",
"description": "Arrival city IATA 3-letter code (e.g. SHA for Shanghai, BJS for Beijing)"
},
"date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Flight date in YYYY-MM-DD format. IMPORTANT: If the user input contains only month and day, use getTodayDate to determine the year. For today's date, use getTodayDate instead of hardcoding."
}
},
"required": [
"date"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
} | — | | — |
searchFlightsByNumberSearch a flight by flight number and date. The flight number must include the airline code, for example MU2157 or CZ3969. dep and arr are optional and should only be provided when the exact airports are known. Date must be in YYYY-MM-DD format. For today's date, use getTodayDate instead of hardcoding.Input schema{
"type": "object",
"properties": {
"fnum": {
"type": "string",
"pattern": "^[A-Z0-9]{2,3}[0-9]{1,4}$",
"description": "Flight number including airline code (e.g. MU2157, CZ3969)"
},
"date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Flight date in YYYY-MM-DD format. IMPORTANT: If the user input contains only month and day, use getTodayDate to determine the year. For today's date, use getTodayDate instead of hardcoding."
},
"dep": {
"type": "string",
"minLength": 3,
"maxLength": 3,
"pattern": "^[A-Z]{3}$",
"description": "Departure airport IATA 3-letter code (e.g. HFE for Hefei)"
},
"arr": {
"type": "string",
"minLength": 3,
"maxLength": 3,
"pattern": "^[A-Z]{3}$",
"description": "Arrival airport IATA 3-letter code (e.g. CAN for Guangzhou)"
}
},
"required": [
"fnum",
"date"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
} | — | | — |