Skip to main content
Glama

create_booking_session

Ouvre une session de réservation à l’Hôtel-Rooftop Les Voiles (Toulon, Mourillon) — ou au Best Western Plus La Corniche avec property_id: "corniche" — pour des dates et une occupation données. Le plus simple : check_in, check_out (AAAA-MM-JJ) et adults. La forme UCP booking.stays[] est acceptée aussi. Rend la chambre et le tarif réellement disponibles, le prix total en centimes d’euro, et une URL pour finaliser. Seuls les tarifs PRÉPAYÉS se réservent par agent : le séjour est réglé en totalité à la réservation, et n’est pas remboursable. Rend une erreur claire si l’hôtel est complet ou fermé sur la période.

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": {
      "booking": "<booking>"
    },
    "name": "create_booking_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
metaNoMétadonnées de protocole UCP.
adultsNoNombre d’adultes (2 par défaut). Forme courte.
bookingYes
check_inNoDate d’arrivée, AAAA-MM-JJ. Forme courte, équivaut à booking.stays[0].stay_dates.start_date.
check_outNoDate de départ, AAAA-MM-JJ. Forme courte.
property_idNoL’hôtel : « corniche » (Best Western Plus La Corniche) ou « voiles » (Hôtel-Rooftop Les Voiles), ou son identifiant (`list_properties`). Absent = Hôtel-Rooftop Les Voiles.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / property_id
      Added value: +{
      +  "description": "L’hôtel : « corniche » (Best Western Plus La Corniche) ou « voiles » (Hôtel-Rooftop Les Voiles), ou son identifiant (`list_properties`). Absent = Hôtel-Rooftop Les Voiles.",
      +  "type": "string"
      +}
  2. Changed3 schema fields changed
    • addedInput schema / properties / adults
      Added value: +{
      +  "description": "Nombre d’adultes (2 par défaut). Forme courte.",
      +  "type": "integer"
      +}
    • addedInput schema / properties / check_in
      Added value: +{
      +  "description": "Date d’arrivée, AAAA-MM-JJ. Forme courte, équivaut à booking.stays[0].stay_dates.start_date.",
      +  "type": "string"
      +}
    • addedInput schema / properties / check_out
      Added value: +{
      +  "description": "Date de départ, AAAA-MM-JJ. Forme courte.",
      +  "type": "string"
      +}
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true), the description discloses commercially critical behavior: prepaid-only rates, full payment at time of booking, non-refundable, and a clear error when the hotel is full or closed. It also states the return shape (room, rate, total price in cents, finalization URL). What it omits is session lifetime/expiry and any authentication context.

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?

The purpose and property scope are front-loaded, followed by the simplest parameter combination, the return values, and the prepaid constraint — a logical order with no filler. It is somewhat long for a single tool, but each sentence carries either a calling instruction or a commercial constraint.

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?

For a six-parameter tool with nested objects and no output schema, the description explains the preferred flat parameters, the alternative nested form, the returned room/rate/price/URL, and the payment terms — everything needed to call it and interpret the result. The only residual ambiguity is that the schema marks `booking` required while the description promotes the short form, which a careful agent must reconcile.

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?

With 83% schema description coverage the schema already documents check_in/check_out format, adults default of 2, property_id values and default, and the booking.stays shape. The description largely repeats these and only adds the preference for the short form over the UCP form, so the baseline of 3 is appropriate.

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?

The description names a specific verb and resource ("Ouvre une session de réservation") and scopes it to two named properties, so the agent knows exactly what is created. It does not explicitly differentiate itself from the close siblings create_rooftop_reservation or get_rooftop_availability, leaving the agent to infer the boundary.

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?

It gives practical calling guidance ("Le plus simple : check_in, check_out et adults", UCP form also accepted) and a real constraint ("Seuls les tarifs PRÉPAYÉS se réservent par agent"). However it never states when to pick this tool over create_rooftop_reservation or get_rooftop_availability, so the usage context is implied rather than explicit.

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