Skip to main content
Glama

Get prices and extras

booking_detail
Read-onlyIdempotent

Return date-specific availability, pricing, extras and booking choices.

Use id_boat and id_tbf1 exactly as returned by search_boats. This tool is for a selected yacht and charter period. Do not call this tool only to see yacht photos or media; call boat_details with the exact id_boat instead. Any Images included here are supplemental booking-context images, while boat_details is the canonical source for the complete public media URLs.

Show all optional extras. After the customer changes extras, passenger count, currency, ports or payment options, call booking_detail_mod and use only its server-calculated totals. When asked for the total, quote customer_cost_summary.full_customer_cost; deposits are returned separately and are not included in that amount. Finally, offer a request for an option or a request for a booking.

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": {
      "id_tbf1": "<id_tbf1>",
      "id_boat": "<id_boat>",
      "dateStart": "<dateStart>",
      "dateEnd": "<dateEnd>",
      "pax": "<pax>"
    },
    "name": "booking_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
paxYesNumber of passengers.
dateEndYesEnd date in DD/MM/YYYY format.
id_boatYesExact yacht ID returned by search_boats.
id_tbf1YesExact pricing ID returned by search_boats.
dateStartYesStart date in DD/MM/YYYY format.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare a read-only, idempotent, non-destructive call, and the description adds genuinely new behavior: deposits are returned separately and are excluded from customer_cost_summary.full_customer_cost, so the total must be quoted from that field. It also discloses that images here are supplemental rather than canonical, and that server-calculated totals from booking_detail_mod supersede anything local.

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?

Front-loaded with the core purpose, then organized into selection, media caveat, extras, and follow-up-workflow paragraphs. Slightly long, with the media caveat stated twice (supplemental images, then boat_details as canonical), which costs a point on tightness.

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 five required parameters and no output schema, the description carries the return-value burden itself by naming customer_cost_summary.full_customer_cost and noting deposits are separate. It also covers the sales workflow end-to-end, including offering a request for an option or a booking, so nothing needed to call it correctly is missing.

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 100%, so the baseline is 3; the description earns extra by specifying that id_boat and id_tbf1 must be used exactly as returned by search_boats rather than guessed or reused across charters. It adds no further detail on date format or pax semantics, which the schema already handles.

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 set: returning date-specific availability, pricing, extras and booking choices for a selected yacht and charter period. It also explicitly carves out scope against the boat_details sibling, which is about media rather than pricing.

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 when-to-use (after selecting a yacht and charter period via search_boats, passing id_boat and id_tbf1 verbatim), when-not-to-use (not for yacht photos or media), the alternative to use instead (boat_details), and the follow-up path (booking_detail_mod after any change to extras, pax, currency, ports or payment options).

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