Skip to main content
Glama

View cabin headline history

get_cabin_price_history
Read-onlyIdempotent

Read lowest returned cabin prices across promotions. Use headlinePriceHistory[].id from get_sailing as seriesKey. Fare and category changes are explicit; missing observations do not establish unavailability.

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": {
      "sailingId": "<sailingId>",
      "seriesKey": "<seriesKey>"
    },
    "name": "get_cabin_price_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateToNo
dateFromNo
maxPointsNo
sailingIdYes
seriesKeyYes

Output Schema

NameRequiredDescriptionDefault
kindYes
seriesYes
sailingIdYes
truncatedYes
priceContextYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / series / properties / guestCount / type
      Previous value: -"number"New value: +[
      +  "number",
      +  "null"
      +]
  2. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent and non-destructive, so safety is covered. The description does add genuine value with the caveat that missing observations do not establish unavailability and that fare/category changes surface explicitly, but it says nothing about ordering, density or pagination behavior of the returned series.

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

Conciseness5/5

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

Two tight sentences plus a critical caveat clause, with the core action front-loaded and no filler. Every clause carries information the agent cannot get from the schema.

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?

An output schema exists, so return-shape explanation is not required, and the sparse-data semantics are covered. The only gap is guidance on the time window and point cap, which matter for a history series but go unmentioned.

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 description carries the burden; it explains the origin and meaning of seriesKey but says nothing about dateFrom/dateTo boundaries or what maxPoints truncation does to the series. The remaining parameters are only guessable from their names.

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?

Names a specific verb (Read) and resource (lowest returned cabin prices) and scopes it to promotions, so the agent knows exactly what data comes back. It does not differentiate itself from the sibling get_price_history, leaving the agent to infer whether that tool covers a different price series.

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?

Gives concrete routing guidance: obtain seriesKey from headlinePriceHistory[].id on get_sailing, which is exactly the prerequisite an agent needs. It stops short of saying when to prefer this over get_price_history or compare_sailings.

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