Skip to main content
Glama

Status of a shared Cruise Planner plan

get_plan_status
Read-onlyIdempotent

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.

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": "get_plan_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_refNoplan_ref from plan_cruise_trip, instead of share_token. Returns stage progress only; plan_cruise_trip returns the links.
share_tokenNoShare token (24 characters) or the full share link. Required unless plan_ref is given.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / plan_ref
      Added value: +{
      +  "description": "plan_ref from plan_cruise_trip, instead of share_token. Returns stage progress only; plan_cruise_trip returns the links.",
      +  "type": "string"
      +}
    • changedInput schema / properties / share_token / description
      Previous value: -"Share token (24 characters) or the full share link. Required."New value: +"Share token (24 characters) or the full share link. Required unless plan_ref is given."
    • removedInput schema / required
      Removed value: -[
      -  "share_token"
      -]
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations it discloses substantive behavior: the privacy rule that signed-in members' plans return only existence and the link, plus the full semantics of each stage status (pending vs undecided vs not_on_sale vs self_booked, etc.). It also explains that ui_language affects only UI chrome and not plan content or narrative answers, and that plan_language reflects stored content and PDF language.

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 and inputs are front-loaded, followed by return content and status vocabulary, so structure is sound and every block is relevant. The status glossary is verbose and reads like reference documentation, with some redundancy ('undecided = left for later or none found…'), which keeps it below top marks.

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?

With no output schema, the description carries the return-value burden and does so thoroughly: stage list, completeness flag, links, the full status vocabulary, privacy behavior, and the two language fields. 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 description coverage is 100%, so the parameters are already fully documented, including the share-token-vs-link and plan_ref exchange. The description restates the accepted input forms ('…/trip/s/<token>' or plan_ref) but adds no format or constraint detail beyond the schema, so it sits at the baseline.

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?

The opening sentence names a specific verb and resource ('Check a Cruise Planner trip plan that the traveler shared with you') and immediately enumerates the return package: stage fill state, completeness, and links to the plan and its PDF. It also distinguishes itself from plan_cruise_trip by noting plan_ref comes from that tool.

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?

It states the precondition (a plan the traveler shared with you) and the three accepted inputs, which is clear context for invocation. It stops short of explicit exclusions, e.g. it never says when to prefer plan_cruise_trip or start_cruise_plan over this status check, leaving that comparison to the reader.

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