Build a full trip plan for a chosen cruise
plan_cruise_tripBuild a complete Cruise Planner(크루즈 플래너) trip plan around a cruise the traveler has already chosen: flights, hotels before and after the cruise, and a plan for each port day. First call: ship_name and departure_date (plus nights or embark_port when several sailings share the ship and date). The response gives plan_ref and missing_fields. Answers for missing_fields are accepted in the same call or in a later call with plan_ref. When nothing is missing, planning starts on our side and can take several minutes. A call with plan_ref also reports progress. When status is "ready", share_url opens the finished trip guide (no sign-in needed) and pdf_url downloads it. The plan language and the default home airport are fixed by the first call (user_language). Responses carry status, plan_ref, open questions, stage progress and, when ready, links and plan_itinerary (the day-by-day plan, without prices). Does not search, compare, price or book cruises.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "plan_cruise_trip"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| pace | No | Preferred pace in port as a short phrase (e.g. "relaxed", "packed"). Optional; accepted together with port_interests or after port_interests was recorded. | |
| cabins | No | Number of cabins, asked when three or more paying travelers (adults and children) share the trip. Accepted together with travelers or after travelers was recorded. | |
| nights | No | Number of nights. Optional; narrows the match when several sailings share the ship and date. | |
| walking | No | How much walking suits the group: normal or easy. Optional; accepted like pace. | |
| plan_ref | No | Reference from an earlier plan_cruise_trip response. Use it for every call after the first. Each response returns a fresh plan_ref, valid for 7 days from that response. | |
| companion | No | Who is traveling: couple, solo, family (with children), parents (with the traveler's parents), friends. | |
| ship_name | No | Exact English ship name (e.g. "MSC World Europa"). Required on the first call (without plan_ref). Matched exactly, not by similarity; an unknown name returns the covered ships (catalog_ships). | |
| travelers | No | Number of travelers. children are ages 2-17, infants are under 2. | |
| embark_port | No | Embarkation port name or UN/LOCODE. Optional; narrows the match like nights. | |
| home_airport | No | City or airport the traveler flies from (name or IATA code). Asked for English-language plans; Korean-language plans default to Incheon (ICN). | |
| user_language | No | The traveler's language as a BCP 47 tag (e.g. "en", "ja", "ko"). Required on the first call (without plan_ref). The first call fixes the plan language: Korean (ko or ko-*) makes a Korean plan with Incheon (ICN) as the default home airport; English (en or en-*) and any other language or invalid tag makes an English plan, and home_airport is then asked. On later calls it sets only the language of the returned links (ui_language). | |
| departure_date | No | Embarkation date, YYYY-MM-DD (local date at the embarkation port). Required on the first call. | |
| port_interests | No | What the traveler likes to do in port, as short phrases (e.g. "old town walks", "local food", "beaches"). Up to 8. |