Skip to main content
Glama

Start a booking

start_booking

Start a booking and get a secure checkout link for the guest. Nothing is reserved until the guest pays on that link (valid 24 hours). Only works at campsites that take payment online (assistant_can_book is true); elsewhere send the guest to the booking_url to book themselves. Requires the guest's name and email, which the campsite uses for the confirmation. Confirm every detail with the guest first. Rate limited.

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": {
      "campsite": "<campsite>",
      "accommodation_id": "<accommodation_id>",
      "check_in": "<check_in>",
      "check_out": "<check_out>",
      "adults": "<adults>",
      "guest": "<guest>"
    },
    "name": "start_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
dogsNoNumber of dogs.
guestYesThe person making the booking. Only pass real details the guest has agreed to share.
notesNoA message for the campsite (arrival time, requests).
adultsYesNumber of adults.
extrasNoOptional extras from get_campsite (electric hook-up, firewood, late checkout...).
answersNoAnswers to the campsite's booking_questions from get_campsite, keyed by question id. Required questions must be answered.
infantsNoNumber of infants, only at campsites whose age_policy has infants_under_age. Infants are never charged.
campsiteYesThe campsite slug, as returned by search_campsites.
check_inYesArrival date, YYYY-MM-DD.
childrenNoNumber of children. Which ages count as a child varies by campsite: see age_policy on get_campsite (default: everyone under 18).
check_outYesDeparture date, YYYY-MM-DD. Must be after check_in.
child_agesNoOne age per child, if known.
voucher_codeNoA gift voucher code, if the campsite sells them.
discount_codeNoA promotional code the guest has, if the campsite accepts them.
club_membershipNoRequired when get_campsite lists a members-only club under club_memberships. status "member" with the guest's membership identifier in "number" (a membership number, or where the club's identifier is "email", such as the Greener Camping Club, the email address the membership is registered to), or "join" where the club allows joining at booking (the fee is added to the total).
accommodation_idYesaccommodation_id from check_availability or get_campsite.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / club_membership / properties / status / description
      Added value: +"\"member\" if the guest already belongs to the club, \"join\" to join at booking where the club allows it."
    • addedInput schema / properties / extras / items / properties / extra_id / description
      Added value: +"The extra's id from get_campsite."
    • addedInput schema / properties / extras / items / properties / quantity / description
      Added value: +"How many of this extra. Default 1."
    • addedInput schema / properties / guest / description
      Added value: +"The person making the booking. Only pass real details the guest has agreed to share."
    • addedInput schema / properties / guest / properties / phone / description
      Added value: +"The guest's phone number, if they want the campsite to have it."
  2. Changed3 schema fields changed
    • changedInput schema / properties / club_membership / description
      Previous value: -"Required when get_campsite lists a members-only club under club_memberships. status \"member\" with the guest's membership number, or \"join\" where the club allows joining at booking (the fee is added to the total)."New value: +"Required when get_campsite lists a members-only club under club_memberships. status \"member\" with the guest's membership identifier in \"number\" (a membership number, or where the club's identifier is \"email\", such as the Greener Camping Club, the email address the membership is registered to), or \"join\" where the club allows joining at booking (the fee is added to the total)."
    • addedInput schema / properties / club_membership / properties / number / description
      Added value: +"Membership number, or membership email for clubs whose identifier is email."
    • changedInput schema / properties / club_membership / properties / number / maxLength
      Previous value: -40New value: +255
  3. Changed2 schema fields changed
    • changedInput schema / properties / children / description
      Previous value: -"Number of children (under 18)."New value: +"Number of children. Which ages count as a child varies by campsite: see age_policy on get_campsite (default: everyone under 18)."
    • addedInput schema / properties / infants
      Added value: +{
      +  "default": 0,
      +  "description": "Number of infants, only at campsites whose age_policy has infants_under_age. Infants are never charged.",
      +  "maximum": 20,
      +  "minimum": 0,
      +  "type": "integer"
      +}
  4. Changed1 schema field changed
    • addedInput schema / properties / club_membership
      Added value: +{
      +  "description": "Required when get_campsite lists a members-only club under club_memberships. status \"member\" with the guest's membership number, or \"join\" where the club allows joining at booking (the fee is added to the total).",
      +  "properties": {
      +    "club": {
      +      "description": "The club key from club_memberships.",
      +      "type": "string"
      +    },
      +    "number": {
      +      "maxLength": 40,
      +      "type": "string"
      +    },
      +    "status": {
      +      "enum": [
      +        "member",
      +        "join"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "club",
      +    "status"
      +  ],
      +  "type": "object"
      +}
  5. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly=false, idempotent=false, and openWorld=true, so the description's job is to add the consequences: nothing is reserved until payment, the link expires after 24 hours, and the call is rate limited. Those are exactly the right disclosures for a non-destructive but non-idempotent mutation. It stops short on failure handling (what happens if checkout is abandoned or a slot is taken in the interim) and gives no indication of the rate limit's shape, which keeps it off a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action and its output, then preconditions, then constraints, then cautions. Every sentence carries a distinct obligation (payment semantics, eligibility check, required inputs, confirmation step, rate limit) with no restatement of the name or title.

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 16-parameter, nested-object mutation with no output schema, the description covers the commercial semantics (nothing reserved until payment), the eligibility gate, and the return value in general terms (a checkout link). The remaining gaps — how the link behaves on expiry and what a successful versus failed start returns — are modest given how thoroughly the schema documents the inputs.

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% with nested guest, extras, club_membership, and answers objects all self-documented, so the baseline is 3. The description adds meaning on top by explaining what the guest object is used for (the campsite sends the confirmation to that name and email) and by framing which details the guest must have agreed to share.

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?

States a specific verb and outcome: "Start a booking and get a secure checkout link for the guest." This is clearly distinct from the siblings check_availability, get_campsite, get_quote, and search_campsites, which are all read/quote operations, so an agent can route correctly without opening a 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?

Gives an explicit precondition (only at campsites where assistant_can_book is true), an explicit when-not plus the alternative (send the guest to booking_url to book themselves), and a procedural rule (confirm every detail with the guest first). The required guest name and email are called out as a precondition rather than left to the schema.

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