Skip to main content
Glama

Compare yachts

compare_boats
Read-onlyIdempotent

Compare 2 to 4 boats using Sedna's date-specific customer pricing.

  • boat_ids: list of 2..4 boat ids

  • pax: customer passenger count used by booking_detail pricing

  • currency: EUR, USD, CNY (default EUR)

  • start_date/end_date: optional availability window (YYYY-MM-DD)

For dated comparisons, customer_cost_summary clearly separates charter price, mandatory extras, full customer cost and refundable deposit. The full customer cost comes from the same booking preview as booking_detail; the refundable deposit is always separate. Cabin fields explicitly label total, double, single and bunk cabins.

Length and beam are optional fleet-supplied facts. Missing values are omitted rather than returned as zero/null or estimated, and must not make an otherwise valid yacht unavailable for comparison.

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": {
      "boat_ids": "<boat_ids>",
      "pax": "<pax>"
    },
    "name": "compare_boats"
  }
}

Input Schema

NameRequiredDescriptionDefault
paxYes
boat_idsYes
currencyNoEUR
end_dateNo
start_dateNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / pax
      Added value: +{
      +  "type": "integer"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "boat_ids"
      -]New value: +[
      +  "boat_ids",
      +  "pax"
      +]
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive, and the description adds real behavioral context beyond them: cost fields come from the same booking preview as booking_detail, the refundable deposit is always separate, and missing length/beam are omitted rather than zeroed or treated as unavailability.

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 sentence first, then a compact parameter bullet list, then output semantics. Every block earns its place, though the output-field prose overlaps with the existing output schema.

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?

Given an output schema exists, the description needn't explain return values, yet it still clarifies the cost breakdown and cabin labeling accurately. With all five parameters addressed and the annotation safety profile confirmed, an agent has everything needed to call it correctly.

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 0% and the schema has no descriptions, so the description carries the load — it defines boat_ids cardinality (2..4), what pax means for booking_detail pricing, the currency options and default, and the YYYY-MM-DD format plus optionality of the dates. It does not clarify what happens if end_date precedes start_date, keeping it below 5.

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?

Opens with a specific verb+resource: comparing 2 to 4 boats with date-specific customer pricing. It is clearly distinct from booking_create/booking_detail by being a comparison, though it never names search_boats or boat_details, so sibling differentiation is only partial.

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

Usage Guidelines3/5

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

Usage is implied by 'Compare 2 to 4 boats' and the dated-window note, and it references booking_detail as the pricing source, but there is no explicit when-to-use vs search_boats or boat_details, and no statement of exclusions.

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