Skip to main content
Glama

Getting to and from the ship

plan_cruise_connections
Read-onlyIdempotent

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").

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "embark_port": "<embark_port>",
      "embark_date": "<embark_date>",
      "disembark_date": "<disembark_date>"
    },
    "name": "plan_cruise_connections"
  }
}

Input Schema

NameRequiredDescriptionDefault
originNoTraveler's home city or airport (name or IATA code). Optional, no default.
embark_dateYesEmbarkation date, YYYY-MM-DD. Required.
embark_portYesEmbarkation port name (English or Korean) or UN/LOCODE. Required. Matched exactly, not by similarity; if not found, the response suggests up to 5 similar guide ports (port_candidates), and their port_key is accepted here.
user_languageNoThe traveler's language as a BCP 47 tag (e.g. "en", "ja", "ko", "zh-TW"). Korean (ko or ko-*) or a missing value opens Korean UI; English (en or en-*) and any other language or invalid tag opens English UI. Valid tags are used for anonymous usage statistics and preserved as a language hint in a chosen-cruise start link. It does not translate narrative answers or saved plan content. The returned ui_language reports the language actually used.
disembark_dateYesDisembarkation date, YYYY-MM-DD. Required.
disembark_portNoDisembarkation port (same matching as embark_port). Optional; defaults to embark_port (round trip).
embark_ship_departure_timeNoShip departure time on embarkation day (local HH:mm). Optional; enables the latest same-day landing time.
disembark_ship_arrival_timeNoShip arrival time on disembarkation day (local HH:mm). Optional; enables the earliest safe flight departure time.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false; the description reinforces this by confirming the data comes from the Cruise Planner port guide rather than live sources. Beyond annotations it discloses non-obvious behavior: exact port matching with up to 5 port_candidates fallback, origin having no default and no assumed country, and which output fields come back in Korean. It does not cover response size limits or pagination, but the safety and data-source profile is well served.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose sentence is front-loaded and the scope limitation is stated explicitly. The long enumerated returns sentence is dense with parentheticals but earns its place because there is no output schema to explain the response shape.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 8 parameters, no output schema, and a read-only openWorld=false profile, the description carries the right load: it explains the returned fields, the port-matching failure path, and the language behavior. Some minor gaps remain, such as how transfer options are ordered or what happens when origin is omitted beyond "no default."

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so parameters are already documented; the description nonetheless adds meaning about origin (optional, no default, no country inferred) and about the Korean text_fields/text_language interaction, which the schema only partially conveys. It also interprets the date_plan and same-day-arrival structure in terms of how the input dates are used, giving the agent a clearer model of parameter effects.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ("Plan how to get to and from a cruise") and immediately enumerates the concrete outputs: gateway airport with IATA code and distance, recommended arrival date, earliest safe flight time, terminal transfers, and hotel location guidance. The negative scope statement ("Does not search live flights or hotel prices") plus the airport/transfer focus clearly separates it from port_day_guide and get_plan_status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Establishes the calling context clearly: supply embarkation/disembarkation ports and dates, and it returns per-port connection guidance. It also sets a boundary by stating it does not search live flights or hotel prices, telling the agent when this tool is insufficient. It stops short of naming an alternative tool for live pricing or flight search.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources