Skip to main content
Glama

Get commercial cruise

cruise_get
Read-onlyIdempotent

Read the complete commercial Cruise and linked CruiseDay fields, including soft-deleted items and version. Null and empty fields are omitted. Omit cruiseId to read the trip version before creation. For commercial cruise reservations and sea/port days use cruise_* tools. Never substitute Activity, CruiseActivity or another segment type for a cruise day. Ordinary shore excursions remain valid Activity/CruiseActivity. If cruise tools are unavailable explain the limitation and ask for clarification.

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": {
      "tripId": "<tripId>"
    },
    "name": "cruise_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
tripIdYes
cruiseIdNo

Output Schema

NameRequiredDescriptionDefault
resultYes
statusYes
successYes
contractVersionYes

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 readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new behavioral facts beyond them: soft-deleted records are returned, version is exposed, and null/empty fields are omitted from the response. It stops short of describing pagination or size limits, which keeps it from a 5.

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 inclusion scope are front-loaded, then conditional usage, then guardrails — a logical progression with no filler sentences. It runs longer than most definitions, but each later sentence (Activity substitution, shore excursions, unavailable-tools fallback) carries a distinct rule rather than restating the purpose.

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?

For a read tool with full annotations and an output schema, the description covers what an agent needs to pick and invoke it, including the soft-delete/version semantics that the structured fields do not express. The only gap is tripId's meaning, which is minor given the domain naming and existing output schema.

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 0%, so the schema supplies names and types only. The description clarifies the semantic effect of omitting cruiseId (read the pre-creation trip version), but tripId is never explained beyond its required status, and no format or validity constraints are added. Partial compensation for a two-parameter tool.

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?

States a specific verb and resource — 'Read the complete commercial Cruise and linked CruiseDay fields' — and immediately scopes what is included (soft-deleted items, version). It also distinguishes this read tool from the cruise_* mutation/reservation family, so an agent can identify it without opening sibling schemas.

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

Usage Guidelines5/5

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

Gives explicit conditional usage: 'Omit cruiseId to read the trip version before creation,' which tells the agent exactly when to call it without the ID. It also routes reservation and sea/port-day work to cruise_* tools and explicitly excludes substituting Activity/CruiseActivity for a cruise day while noting shore excursions remain valid — real when/when-not guidance.

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