Mercury Jets

Look up airports suitable for private charter flights and return their ICAO, IATA and FAA codes. Use when the user asks which airports serve a place for a charter flight, asks for an airport's code, or wants to choose between the airports of one city while arranging a charter. Required: query — a city name, airport name, or ICAO/IATA/FAA code, at least two characters. Optional: limit, 1 to 10, default 5. Returns up to `limit` airports, each with its name, municipality, region, and the codes that airport has — ICAO, IATA, or a local code where it has no IATA. Results come back in the order the airport service ranks them for the query. Airports in Ukraine, Russia, Iran, Belarus, North Korea and South Sudan are omitted from results: charter flights to or from those countries cannot be arranged under current U.S. regulatory restrictions. The response says so when any were omitted. Not for commercial airline routes, airport facilities, or ground transport.

search_airports

Look up specifications for a private aircraft model, category or tail number and display them as an info card. Use when the user asks about a private aircraft model, compares models, asks which aircraft fall into a category, or gives a tail number to look up, while researching or arranging a charter flight. Required: query — an aircraft model name, model code, category, or tail number, for example 'Citation X', 'G650', 'light jet', 'N123XX'. Optional: category, to narrow results to one category; max_results, default 5; flight_search_id and cta_redirect_url, when a flight-results message includes them (cta_redirect_url adds an Inquire button linking back to the site). Returns, for each match: model, category, passenger capacity, cabin dimensions, tail number, year manufactured, year refurbished, WiFi availability, ARGUS and Wyvern safety certifications, and in-flight features. Range and baggage volume are not available through this tool.

get_aircraft_info

Search live charter prices for a private flight between two airports and display the results as a widget. Use when the user has asked what a private charter flight costs or what aircraft are available, and has given both a departure and an arrival location. Required on every call: departure and arrival (a city or airport name each), passengers, and departure_date. return_date is also required when flight_type is 'round_trip'. Add departure_code or arrival_code when the exact ICAO or IATA code is known; the codes are sent together with the names. When the user has not given a passenger count or a date, use 2 passengers and a departure date two days from today, and say in the reply which values were assumed; the result echoes the values used so they can be changed. Optional, defaulted by the server when omitted: departure_time (09:00), flight_type ('one_way'), return_time (17:00, round trip only), currency ('USD'). Where a city has several airports, search its main private-jet airport unless the user names another: Miami is Opa-Locka (KOPF), New York is Teterboro (KTEB), Los Angeles is Van Nuys (KVNY), London is Farnborough (EGLF) or Luton (EGGW), Paris is Le Bourget (LFPB), Geneva is LSGG and Dubai is Al Maktoum (OMDW). Name both airports the search used in the reply, so the user can ask for a different one. Charter flights to or from Ukraine, Russia, Iran, Belarus, North Korea and South Sudan cannot be arranged under current U.S. regulatory restrictions. The server declines those searches and returns an explanation to pass on, with nearby unrestricted alternatives where they exist. Returns aircraft options grouped by category, each with a price estimate and an estimated flight time, and a link the user can follow to request a personalised quote. Prices are estimates before taxes and fees. When a route and passenger count cannot be priced instantly, the result has no aircraft and carries a message explaining why; it is not an error. A follow-up about a search already run in this conversation — a category, an aircraft, what a price covers — is answered from that result. Search again when the route, date, time, passenger count or trip type changes. [Current context: Today is Wednesday, October 28, 2026 (2026-10-28), current time is 15:27 local time.]

search_flights

Display an interactive charter search form for the user to fill in. Use when the user wants a charter flight but has not given both a departure and an arrival, or asks to see the search form. The form collects route, date, time, passenger count and trip type in one step, so it stands in for asking those questions one at a time. A form or results shown earlier in the conversation do not replace a new form when the user starts another trip without a complete route. Optional: prefill_departure, prefill_arrival, prefill_passengers and prefill_date carry over anything the user has already said. Set prefill_trip_type='empty_leg' to open the form in empty-leg mode, which offers a date and a flexibility window in place of a return date. Submitting the form runs the search in the widget, which then sends a message that starts with 'The flight-search-form widget was just submitted' and lists a tool and the values entered. That message is the form's result, not a new request: call the tool it names with those arguments. Showing the form again at that point would clear what the user entered. When the user has already given both a departure and an arrival, search_flights prices the trip; a follow-up question about results already shown is answered from those results.

show_flight_search

Search empty-leg flights (one-way repositioning flights with a fixed date and route) and display the results as a widget. Use when the user asks about empty legs, deadhead or repositioning flights. Parameters: departure / departure_code and arrival / arrival_code (the route; a departure and an arrival are both needed), date_from (date searched, today when omitted; a date before today is searched from today), flex_days (days either side of date_from also searched, 1 to 5, default 3), passengers (minimum seats), max_results (default 10). The result states the dates searched and the airports the route resolved to. Legs are listed in the inventory's relevance order. Each end of a leg is marked as an exact match with the required airport or not: a leg that is not an exact match flies from or to another airport, which can be in another city, so name each leg's own airports in the reply. For a city with several airports, search with the city's main private-jet airport and name it in the reply so the user can ask for another. Empty legs fly on a fixed date and route, with no choice of departure time or aircraft; the reply mentions this. Returns a widget listing matching empty-leg flights with prices and an Inquire link to the website. When nothing matches, the result is a text message saying so, without a widget. [Current context: Today is Wednesday, October 28, 2026 (2026-10-28), current time is 15:27 local time.]

search_empty_legs