Tool description (what the LLM sees)
Tool description (what the LLM sees)
Find the cheapest fares for a known origin, destination, and FIXED date using cached pricing. Takes the SAME inputs as flight_calendar, but for one specific departure date (one-way, or with a return date for round-trip) it returns up to ten itineraries sorted cheapest-first.
WHEN TO USE THIS TOOL:
- The user knows the route AND the exact date, and just wants the cheapest options that day.
- Examples: "Cheapest flight Paris → New York on June 15", "What's the lowest fare CDG→JFK on the 15th?".
WHEN TO USE flight_calendar / find_dates INSTEAD:
- The user is flexible on dates (a range or "when should I fly?"), use flight_calendar (full grid) or find_dates (curated date spread).
WHEN TO USE flight_search INSTEAD:
- The user is ready to book and needs live pricing + a bookable token. flight_search hits live pricing.
IMPORTANT:
All dates MUST be in the future. Never use past dates.
Origin and destination must be IATA city codes by default, or IATA airport codes if the user specifies them.
Use trip_type="roundtrip" with a return date for a round-trip; otherwise "oneway".
Flow: lowest_fare → flight_search (price-check) → trip → checkout
PRICES: in the text output, price is already a decimal in major units, display as-is, do NOT divide. In structuredContent, flights[].total_amount and origin_total_amount are objects {value, currency, decimal_places} where value is an INTEGER in minor units, divide value by 10^decimal_places before displaying those (value 15977 with decimal_places 2 is 159.77 USD).
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
origin | string | Yes | Origin airport IATA code or city code (3 letters). Examples: “JFK”, “PAR”. |
destination | string | Yes | Destination airport IATA code or city code (3 letters). Examples: “CDG”, “NRT”. |
trip_type | enum ("oneway" | "roundtrip") | Yes | Trip type: “oneway” or “roundtrip”. |
departure_dates | array<string> | No | Specific departure dates (YYYY-MM-DD). Multiple dates searched with OR logic. |
departure_date_ranges | array<object> | No | Departure date ranges for flexible search. |
departure_date_ranges[].start | string | Yes | Range start date (YYYY-MM-DD) |
departure_date_ranges[].end | string | Yes | Range end date (YYYY-MM-DD) |
return_dates | array<unknown> | No | Specific return dates (YYYY-MM-DD) for round-trip flights. |
return_date_ranges | array<object> | No | Return date ranges for flexible round-trip search. |
return_date_ranges[].start | string | Yes | Range start date (YYYY-MM-DD) |
return_date_ranges[].end | string | Yes | Range end date (YYYY-MM-DD) |
stay_days | integer | No | Exact stay duration in days. Auto-calculates return date. |
stay_days_range | object | No | Flexible stay duration range. Example: {min: 5, max: 10} |
stay_days_range.min | integer | Yes | Minimum stay duration in days |
stay_days_range.max | integer | Yes | Maximum stay duration in days |
direct_only | boolean | No | Only return nonstop flights. |
cabin_class | enum ("economy" | "premium_economy" | "business" | "first") | No | Cabin class filter. |
max_total | number | No | Maximum total price for the trip (canonical name). Preferred over max_price. |
sort_by | enum ("lowest" | "recommendation") | No | Sort order. Default: “lowest” (cheapest first). |
currency | string | No | ISO 4217 currency code. Defaults to “USD”. |
locale | string | No | BCP 47 locale. Defaults to “en-US”. |
format | enum ("text" | "json") | No | Response format. “text” returns plain text for LLMs. “json” returns structured JSON. |
user_intent | string | No | The end user’s current request in their own words, e.g. “find a cheap flight to Tokyo in mid-June”. Pass it as-is when short; otherwise condense the goal and constraints into 1-2 sentences. Strip personal identifiers (names, emails, phone numbers, addresses, payment details), replace them with placeholders like “[name]”. Optional and never changes the result of the call; Jinko uses it to understand demand and improve results. |