Skip to main content
Glama

Send option or booking request

booking_create

Submits a request for a booking or a request for an option.

This action re-prices and submits the request. booking_detail_mod is a stateless preview: selections made there are not stored automatically. Therefore selected_extras MUST repeat every extra the customer selected, using the exact id_opt and quantity. Pass an empty list only when the customer selected no optional extras. Never report an extra as selected unless this tool's saved_extras verification confirms it.

Full client details (name, email, phone) are required to submit the request. **** strong rule: AI should not guess or input customer information on its own. It must ask customers to input it on its own.

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": {
      "client_name": "<client_name>",
      "client_email": "<client_email>",
      "client_phone": "<client_phone>",
      "id_tbf1": "<id_tbf1>",
      "id_boat": "<id_boat>",
      "dateStart": "<dateStart>",
      "dateEnd": "<dateEnd>",
      "pax": "<pax>",
      "selected_extras": "<selected_extras>"
    },
    "name": "booking_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
paxYesNumber of passengers.
modeNoThe type of creation, 'booking' or 'option' (defaults to 'booking').booking
dateEndYesThe end date (DD/MM/YYYY).
id_boatYesThe unique boat identifier.
id_tbf1YesThe TBF1 identifier for the booking.
dateStartYesThe start date (DD/MM/YYYY).
client_nameYesThe client's full name.
client_emailYesThe client's valid email address.
client_phoneYesThe client's contact phone number.
selected_extrasYesRequired complete selection. Example: [{"id_opt": 123, "selected": true, "quantity": 1}]. Use [] only when no optional extra was selected.
arrival_selectedNo
currency_id_deviseNo
departure_selectedNo
arrival_port_pay_optionNo
departure_port_pay_optionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedInput schema / properties / selected_extras / anyOf
      Removed value: -[
      -  {
      -    "items": {
      -      "additionalProperties": true,
      -      "type": "object"
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedInput schema / properties / selected_extras / default
      Removed value: -null
    • addedInput schema / properties / selected_extras / description
      Added value: +"Required complete selection. Example:\n[{\"id_opt\": 123, \"selected\": true, \"quantity\": 1}].\nUse [] only when no optional extra was selected."
    • addedInput schema / properties / selected_extras / items
      Added value: +{
      +  "additionalProperties": true,
      +  "type": "object"
      +}
    • addedInput schema / properties / selected_extras / type
      Added value: +"array"
    • changedInput schema / required
      Previous value: -[
      -  "client_name",
      -  "client_email",
      -  "client_phone",
      -  "id_tbf1",
      -  "id_boat",
      -  "dateStart",
      -  "dateEnd",
      -  "pax"
      -]New value: +[
      +  "client_name",
      +  "client_email",
      +  "client_phone",
      +  "id_tbf1",
      +  "id_boat",
      +  "dateStart",
      +  "dateEnd",
      +  "pax",
      +  "selected_extras"
      +]
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare openWorldHint=true, idempotentHint=false, and destructiveHint=false, so the safety profile is partly covered. The description adds genuinely new behavior: the call re-prices before submitting, the preview is stateless so nothing carries over automatically, and the response includes a saved_extras verification the agent must check before reporting success. Reversibility, permissions, and failure behavior are not described.

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 submission action and its re-pricing behavior are front-loaded, and each subsequent sentence adds a distinct constraint rather than restating the schema. Minor deductions for awkward markup (double-backtick artifacts in booking_detail_mod) and a misplaced emphasis marker around the customer-info rule.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 15-parameter, non-idempotent, open-world mutation with no output schema, the description covers the highest-risk aspects: silent re-pricing, stateless previews, extras fidelity, and the prohibition on fabricating client data. Gaps remain around what happens on partial failure, whether a submitted booking can be amended or cancelled, and what the undefined optional fields control.

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?

Schema coverage is 67%, so the baseline is 3. The description meaningfully enriches selected_extras (must mirror the customer's exact id_opt/quantity, empty list only when nothing was selected) and stresses that client_name/email/phone must come from the customer. However, arrival_selected, departure_selected, currency_id_devise, and the two port-pay options remain undocumented in both schema and description.

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?

The description names a specific verb and resource ("Submits a request for a booking or a request for an option") and immediately differentiates it from the sibling booking_detail_mod, which is characterized as a stateless preview rather than a submission. An agent can tell the two apart without opening either 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?

It clearly states when to use this tool versus booking_detail_mod (preview vs. actual submit) and imposes a hard constraint that selected_extras must repeat every prior selection with exact id_opt and quantity. It also forbids the AI from inventing customer details and requires asking the customer. Lacks explicit guidance on when to choose 'option' mode over 'booking' mode beyond the parameter default.

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