Skip to main content
Glama

create_booking

Destructive

Create a booking for a tourism service.

Pass children_count whenever the party includes children, and
quoted_total_minor with the total you last quoted, so a price that moved
between the quote and the booking is refused rather than silently charged.

IMPORTANT: This only RESERVES the booking — it is NOT confirmed until paid.
Ask the traveller for their email and phone. Show the exact held email and phone
values and ask for a correction if either is wrong; never guess or auto-apply a
suggestion.

Verification: if the response is contact_verification_required, a six-digit
code has been emailed to the traveller. Ask them to read it out, then call
the SAME tool again, create_booking, with the SAME arguments you sent the
first time plus verification_code=<code>. That second call IS the submission
of the code; there is no separate verify tool, and there is nothing for the
traveller to do on soley.travel. The response repeats this in next_action
and hands your own arguments back in retry_with. Never tell the traveller
that no action exists for the code.

Multi-stop trips: if the tourist is booking several operators in one
trip (e.g. hotel + tour + activity), call create_booking for EACH leg
FIRST. Do NOT call get_payment_link between bookings — that produces
multiple separate links. Leave trip_token empty on the first leg; the
response returns a 'trip_token' — pass that same token on every later leg
of this trip. Once every leg is reserved, call get_payment_link ONCE with
any one booking_reference; the server bundles exactly this trip's legs
(by trip_token) into a single consolidated payment link.

Never tell the user a booking is confirmed until payment is complete.
The response transaction_mode is demo, sandbox, or live. If demo_notice is
present, relay it exactly; do not describe a sandbox booking as live or
chargeable.
Requires OAuth2 authentication.

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": {
      "operator_id": "<operator_id>",
      "service_id": "<service_id>",
      "check_in": "<check_in>",
      "check_out": "<check_out>",
      "guest_name": "<guest_name>",
      "guest_phone": "<guest_phone>",
      "guest_count": "<guest_count>",
      "guest_email": "<guest_email>"
    },
    "name": "create_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelNoVerification delivery chosen by the traveller. Email is the default. SMS falls back to email when Twilio Verify is unavailable.email
check_inYesArrival date in ISO format (YYYY-MM-DD), e.g. '2026-06-15'.
check_outYesDeparture date in ISO format (YYYY-MM-DD), e.g. '2026-06-18'.
time_slotNoOptional time slot in HH:MM format, e.g. '15:00'. Required for scheduled services like Lava Show.
guest_nameYesFull name of the guest making the booking.
service_idYesService identifier for a specific room type, tour, or activity. Obtain from get_services using the operator_id.
trip_tokenNoTrip token that groups the legs of ONE trip for a single payment. Leave EMPTY on the first booking of a trip — the response returns a fresh 'trip_token'. Pass that SAME token on every subsequent create_booking for the same trip so the consolidated payment link covers exactly this trip and nothing else.
guest_countYesThe TOTAL number of travellers, including any children. For two adults and one child pass guest_count=3, adults_count=2, children_count=1, NOT guest_count=2. Getting this wrong books too few seats and the operator's manifest is short a person on the day.
guest_emailYesGuest email address for booking confirmation, e.g. 'tourist@example.com'.
guest_phoneYesGuest phone number in international format, e.g. '+3548001234'. Icelandic numbers: '+354' followed by 7 digits.
operator_idYesUnique operator slug, e.g. 'fosshotel-reykjavik' or 'arctic-adventures'. Obtain from search_operators. Do not guess — always look up first.
adults_countNoHow many of guest_count are adults. Optional, but always pass it: when given, adults_count + children_count must equal guest_count, and the call is refused if it does not, rather than booking the wrong party.
children_countNoHow many of guest_count are children. Pass this whenever any traveller is a child and the service lists a child price.
quoted_currencyNoCurrency of quoted_total_minor, e.g. 'ISK'. Defaults to the service's own settlement currency.
special_requestsNoOptional guest requests, e.g. 'late check-in' or 'ground floor room'. Do not include card numbers, identity documents, or medical records.
verification_codeNoSix-digit code the traveller received after create_booking returned contact_verification_required. Submitting the code IS calling the SAME tool again: create_booking, with the SAME arguments you sent the first time, plus verification_code=<code>. There is no separate verify tool and nothing for the traveller to do on soley.travel. The error response repeats this in next_action and hands your own arguments back in retry_with; follow them.
quoted_total_minorNoThe total you last showed the traveller, in minor units, copied from check_availability's price_total_amount_minor or get_price_quote's total_amount_minor. If it no longer matches the server's price the booking is refused instead of charging a different amount. Always pass it when you have quoted a price.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, and the description goes well beyond them: price-moved-between-quote-and-booking is refused rather than silently charged, a contact_verification_required response triggers a six-digit emailed code, transaction_mode is demo/sandbox/live and demo_notice must be relayed verbatim. It also states the OAuth2 requirement and warns never to claim confirmation before payment, which is exactly the behavior an agent would otherwise guess wrong.

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 action and the reserve-vs-confirm caveat, then grouped into labelled concerns (verification, multi-stop, transaction mode). It is long, but nearly every sentence carries a failure mode the agent would otherwise hit; the only mild duplication is the verification flow being explained in both the prose and the verification_code schema entry.

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 17-parameter destructive booking tool with a retry-after-error flow, the description covers the sequencing (legs before payment link), the error-recovery loop, the auth requirement and the demo/live caveat. Because an output schema exists, it correctly spends no words on return-value shapes and instead explains how to react to the responses it will see.

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 100% across all 17 parameters, and the schema already documents the guest_count/children_count arithmetic, trip_token sequencing, quoted_total_minor price-lock and verification_code retry mechanics. The description restates the intent behind children_count and quoted_total_minor but adds no syntax, format or constraint that the schema lacks, so the baseline 3 applies.

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?

"Create a booking for a tourism service" names a specific verb and resource, and the follow-up sentence sharpens scope further by stating the booking is only RESERVED and not confirmed until paid. That distinction separates it from get_payment_link and get_booking_status without the agent needing to open any schema.

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?

Explicit routing rules are given for the hard cases: call create_booking for each leg of a multi-stop trip, do NOT call get_payment_link between bookings, call it once at the end with any one booking_reference. The verification path is equally explicit — the code is submitted by calling the SAME tool again with the SAME arguments plus verification_code, and there is no separate verify tool to look for.

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