Skip to main content
Glama

Server Details

Plans the trip around a cruise you have already chosen: port days, flights, hotels and transfers.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
Cruise Planner

TDQS

A4/5.0

Scored across 5 tools

Disambiguation3/5

The five tools mostly cover distinct actions, but plan_cruise_trip and start_cruise_plan both target 'a traveler who has chosen a specific cruise and wants the whole trip planned,' differing only in whether planning happens through the API or via a returned planner URL, which invites misselection. get_plan_status also overlaps with plan_cruise_trip's progress reporting via plan_ref. The descriptions do give enough signals to separate them, but only after careful reading.

Naming Consistency4/5

Four of five names use a clear verb_noun pattern (get_plan_status, plan_cruise_connections, plan_cruise_trip, start_cruise_plan) in consistent snake_case. port_day_guide is a noun phrase with no verb, a minor deviation that is still readable and domain-appropriate.

Tool Count4/5

Five tools for a focused cruise-trip planning domain is well within a reasonable range, and each maps to a real step (connections, port day, full plan, status, planner entry). It is slightly thin, and the redundant-feeling plan_cruise_trip/start_cruise_plan pair is the only place where a tool feels less earned.

Completeness3/5

The surface covers pre-cruise logistics, port days, full plan generation, progress checking and a planner hand-off, which is solid lifecycle coverage. However, there is no cruise discovery/search at all beyond an exact-match catalog check in start_cruise_plan, and no way to modify, restart or cancel an existing plan, which are notable gaps for a 'Cruise Planner'.

Available Tools

5 tools
get_plan_statusStatus of a shared Cruise Planner planA
Read-onlyIdempotent
Inspect

Check a Cruise Planner(크루즈 플래너) trip plan that the traveler shared with you. Input the share token or the full share link (…/trip/s/), or the plan_ref of a plan made with plan_cruise_trip. Returns which stages are filled (cruise, brief, flights, hotels, port days), whether the plan is complete, and links to the shared plan and its PDF. Flight and hotel stages: open = not started yet; pending = not decided yet, the planner is still searching; chosen = in the plan; self_booked = the traveler booked it; undecided = left for later or none found, the plan works without it and it can be added in the planner; not_on_sale = flights for these dates are not on sale yet; declined = the traveler said it is not needed; not_needed = not applicable. Plans of signed-in members are private: only their existence and the link are returned. ui_language describes the shared-page UI requested by user_language. plan_language is the stored language of the plan content and its PDF.

Inputs: plan_ref, share_token, user_language.

plan_cruise_connectionsGetting to and from the shipA
Read-onlyIdempotent
Inspect

Plan how to get to and from a cruise. Given the embarkation and disembarkation ports and dates, returns for each port the gateway airport (IATA code and distance), the recommended arrival date (the day before embarkation) and the same-day arrival rule, the earliest safe flight time on disembarkation day, terminal↔airport transfer options from the Cruise Planner(크루즈 플래너) port guide, the cruise terminals and where to stay (city centre vs. near the terminal). date_plan gives the traveler-input embarkation/disembarkation dates, a recommended pre-cruise hotel check-in/check-out, and a separate same-day-arrival alternative. The recommended pre-cruise hotel checks out on embark_date. Does not search live flights or hotel prices. origin (the traveler's home city or airport) is optional and has no default; no country is assumed when it is missing. Fields listed in text_fields are in Korean (text_language "ko").

Inputs: embark_date (required), embark_port (required), disembark_date (required), origin, +4 more.

plan_cruise_tripBuild a full trip plan for a chosen cruiseAInspect

Build 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.

Inputs: pace, cabins, nights, walking, +9 more.

port_day_guidePort day guide (time ashore, nearby destinations, places)A
Read-onlyIdempotent
Inspect

Plan one time-boxed day in an unfamiliar port city — typically a cruise port day, or any stop with a fixed arrival and departure time. Given the port and the ship's local arrival and departure times, returns: the usable time ashore (after disembarking, keeping a safe return margin before all-aboard), each nearby destination with its round-trip travel time, the time left there and a good/tight/skip verdict, up to 8 recommended places, transport routes from the pier with durations and fares, the cruise terminals, and verified facts (closures, entry rules, prices) with source links. Use it for questions like "We are in Livorno 07:00–19:00 — can we see Florence?" or "What can we do in Keelung from 13:00 to 18:00?". Covers 200+ cruise ports from the Cruise Planner(크루즈 플래너) port guide; for a port that does not match it returns the time window and up to 5 similar guide ports. Fields listed in text_fields are in Korean (text_language "ko"). No ratings, reviews or opening hours.

Inputs: port (required), arrival_time (required), departure_time (required), tender, +2 more.

start_cruise_planStart a full trip plan for a chosen cruiseA
Read-onlyIdempotent
Inspect

For a traveler who has chosen a specific cruise (ship + departure date) and wants the whole trip planned around it: flights, hotels before and after the cruise, and every port day. Checks whether Cruise Planner(크루즈 플래너) knows this sailing and returns a link to the planner where the traveler continues. Ship names are matched exactly; one that does not match returns catalog_ships (exact English names by cruise line) with reason ship_not_in_catalog. Returns found / ambiguous / not_found. When found, sailing shows only nights and embarkation port (UN/LOCODE) to confirm the match. When ambiguous, each candidate shows only departure date, nights and that port; nights and embark_port narrow the match. Does not search, compare or price cruises; returns no itinerary, prices, cabins, ship details or sailing identifiers. planner.ui_language reports the UI language ("en" or "ko") of the returned link. planner.url carries the selection token and query parameters that keep the cruise selected.

Inputs: ship_name (required), departure_date (required), nights, embark_port, +2 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources