Skip to main content
Glama

Recalculate price with extras

booking_detail_mod
Read-onlyIdempotent

Apply customer selections and return server-recalculated booking details.

Copy id_boat and id_tbf1 from search_boats. Sedna is the only source of truth for prices: never calculate totals in the LLM. Send selected extras, passenger count, currency, ports and payment options here, then present the complete updated summary returned by the server. This is a stateless price preview and does not save the selection. If the customer proceeds, repeat the complete selected_extras list in booking_create. When the customer asks for the new total, quote customer_cost_summary.full_customer_cost. Explain payable_now and payable_at_base separately; never add them in the LLM, and keep the refundable deposit separate.

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_mod"
  }
}

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.
selected_extrasNoSelected extras with id_opt, selected and quantity.
arrival_selectedNoSelected arrival port ID.
currency_id_deviseNoCurrency ID present in booking_detail rates.
departure_selectedNoSelected departure port ID.
arrival_port_pay_optionNobase or now.
departure_port_pay_optionNobase or now.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, and the description still adds real substance: statelessness, no persistence of the selection, Sedna as the only price source of truth, and a prohibition on LLM-side arithmetic. It also prescribes how to present the result (quote customer_cost_summary.full_customer_cost; explain payable_now and payable_at_base separately; keep the refundable deposit separate), which goes well beyond the annotations.

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 action, followed by sourcing rules, statefulness, and presentation rules in a logical order. It is fairly dense with imperatives, but nearly every sentence carries operational value; only the repeated 'never calculate totals in the LLM' emphasis is slightly redundant.

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?

There is no output schema, and the description compensates by naming the exact return field to quote and how to break down the cost components. For an 11-parameter pricing tool, the agent has everything needed to call it and report results 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 100%, so baseline is 3; the description still adds cross-field meaning by naming which inputs to carry over (extras, passenger count, currency, ports, payment options) and stressing that the extras list must be complete and repeated in booking_create. It does not explain the arrival/departure port vs. pay-option relationship beyond what the schema hints, so it is not a full 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?

States a specific verb and resource: 'Apply customer selections and return server-recalculated booking details,' and clarifies the scope with 'stateless price preview and does not save the selection.' It does not, however, explicitly distinguish itself from the sibling booking_detail (presumably the base version without extras), leaving the agent to infer the difference from the name and title.

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 clear routing: copy ids from search_boats, use this for preview, and 'If the customer proceeds, repeat the complete selected_extras list in booking_create.' That is a strong when-to-use/when-to-go-elsewhere signal. It lacks an explicit statement about when booking_detail rather than booking_detail_mod is appropriate.

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