Skip to main content
Glama

Chiffrer une réservation

quote_booking
Read-onlyIdempotent

Exact price of a basket of services at one centre for a vehicle category, as the booking will charge it: per-line prices, the online-payment discount, off-peak (« heures creuses ») pricing when date and timeSlot are given, and the on-site total. Also returns notIncludedOptions (common needs the basket does not cover, such as seats or pet hair) and thresholdNudge (an option that would unlock the online discount for the same total or less), each possibly empty. An invalid basket returns { error, message } (incompatible_options, missing_formule, service_not_available, online_payment_not_accepted). Promo codes are not accepted here; they are entered on the booking page.

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": {
      "centerSlug": "<centerSlug>",
      "vehicleType": "<vehicleType>",
      "serviceIds": "<serviceIds>",
      "paymentMethod": "<paymentMethod>"
    },
    "name": "quote_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoChosen day, YYYY-MM-DD (Europe/Paris): some slots are cheaper
timeSlotNo
centerSlugYesCentre slug as returned by find_centers or search_available_slots
serviceIdsYesService ids from get_services: one formule, plus any options
vehicleTypeYesvehicleTypes.value from get_center_details (s, m, l, xl, van, moto) — never the label.
paymentMethodYesonline = card at booking (often discounted), on_site = at the centre

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / vehicleType / description
      Previous value: -"vehicleTypes.value from get_center_details (s, m, l, xl, moto) — never the label."New value: +"vehicleTypes.value from get_center_details (s, m, l, xl, van, moto) — never the label."
    • changedInput schema / properties / vehicleType / enum
      Previous value: -[
      -  "s",
      -  "m",
      -  "l",
      -  "xl",
      -  "moto"
      -]New value: +[
      +  "s",
      +  "m",
      +  "l",
      +  "xl",
      +  "van",
      +  "moto"
      +]
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the bar is low, yet the description goes well beyond: it discloses the computed outputs (per-line prices, online-payment discount, off-peak pricing gated on date + timeSlot, on-site total), the advisory fields notIncludedOptions and thresholdNudge with the note that each may be empty, and the full error envelope with enumerated codes.

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 purpose in the first clause, then dense but purposeful enumeration of outputs, advisory fields, and error codes; nothing is filler. The single long sentence covering outputs is slightly heavy, but every clause carries information an agent would otherwise have to discover by calling the tool.

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 no output schema, the description carries the return-shape burden itself and does so thoroughly, including conditional fields (off-peak pricing), possibly-empty advisory fields, and the error contract. For a 6-parameter read-only pricing tool, nothing an agent needs to call it correctly or interpret results appears to be 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 83%, so the baseline is 3, but the description adds real meaning: date and timeSlot only affect price when both are supplied (off-peak 'heures creuses'), and paymentMethod drives the discount. It also hints that an invalid basket is diagnosed via error codes (missing_formule, incompatible_options), which tells the agent how bad inputs surface rather than being silently ignored.

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?

Names a specific verb-equivalent (compute the exact price) plus the resource (a basket of serviceIds at one centre for a vehicle category) and pins scope with 'as the booking will charge it'. That phrasing cleanly separates it from get_booking/start_booking (existing or new bookings) and get_services (catalog lookups), so an agent can pick it without opening the schema.

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 context for use (pricing a basket prior to committing) and an explicit when-not for one dimension: 'Promo codes are not accepted here; they are entered on the booking page.' It does not explicitly state the ordering relative to start_booking (e.g. call this first to preview), so it stops short of naming the alternative and the condition that selects it.

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