Skip to main content
Glama

Start a full trip plan for a chosen cruise

start_cruise_plan
Read-onlyIdempotent

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.

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": {
      "ship_name": "<ship_name>",
      "departure_date": "<departure_date>"
    },
    "name": "start_cruise_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
nightsNoNumber of nights. Optional; helps when several sailings share the ship and date.
ship_nameYesThe exact English ship name, e.g. "MSC Bellissima" or "Norwegian Epic". Required. Matched exactly (case, spacing and punctuation ignored), not by similarity. A name that does not match returns the catalog ships (catalog_ships: English names by cruise line).
embark_portNoEmbarkation port name or UN/LOCODE. Optional; helps when several sailings share the ship and date.
sailing_refNoA cruise search provider's sailing reference for the chosen cruise, passed through as given. Optional.
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.
departure_dateYesEmbarkation date, YYYY-MM-DD, local date at the embarkation port. Required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, and the description adds real behavioral detail beyond them: exact (not similarity) ship matching, the ship_not_in_catalog failure with catalog_ships, the found/ambiguous/not_found outcome space, what each outcome reveals and hides, and that no sailing identifiers, prices or cabins are returned. This is consistent with readOnlyHint — it returns a tokenized link rather than mutating state.

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?

Purpose is front-loaded in the first clause before the mechanics, and each sentence covers a distinct concern (matching, outcomes, exclusions, return fields). Some redundancy: catalog_ships and the exact-match rule appear both in the description and the schema, and the description runs long for a 2-required-parameter tool.

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

Completeness5/5

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

There is no output schema, so the description carries the return contract — and it does: found/ambiguous/not_found semantics, which fields each variant exposes, planner.url carrying the selection token, and planner.ui_language reporting the effective language. An agent has everything needed to call it and interpret the response.

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

Parameters3/5

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

Schema coverage is 100%, so ship_name matching rules, nights, embark_port, sailing_ref and user_language are all already documented in the schema. The description's additions — that nights and embark_port narrow an ambiguous match — largely restate the schema's own wording. Baseline 3 applies because the schema does the heavy lifting.

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

Purpose4/5

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

The description states a precise verb+resource with scope: it starts a whole-trip plan for an already-chosen cruise (ship + departure date) and returns a link to the planner rather than doing the planning. It also delimits what it is not (no searching, comparing, pricing, or itinerary/cabin data). It does not explicitly contrast with plan_cruise_connections or port_day_guide, whose scopes could look adjacent.

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?

The target situation is stated unambiguously: the traveler has already picked a specific sailing and wants flights, pre/post hotels, and port days planned around it. Exclusions are given (does not search, compare or price cruises). No alternative tool is named for those excluded cases, so routing when the cruise is not yet chosen is left to inference.

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