Skip to main content
Glama

Request a booking

request_booking

Lodge a booking. On success this returns a secure checkout_url: give it to the customer to pay directly (their card, never through you). No payment is ever taken through this tool itself. A pickup on a closed day or inside a blackout window is refused (accepted:false) before anything is lodged. Stops on the way (up to 4 each way): stops, and return_stops on a return, the same as the get_quote you quoted; the booking is made at the booking form's own total with the stops in it. An airport pickup needs flight, the flight number they land on, and a return whose way back starts at an airport needs return_flight. The one time there is no flight: the customer is dropping off a hire car at the airport first (hire_car true). Places are checked as in get_quote, and booked where they really are. Booking for someone else (the customer books and pays, another person travels): add passenger_name, passenger_mobile (the driver contacts this number) and passenger_email. When the booking is paid the passenger gets their own confirmation by email, without the price; the customer gets the full confirmation, the receipt and the pay link. Leave them out when the customer is travelling. Requires agent_key (contact admin@cgctransfers.com.au to obtain one).

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": {
      "agent_key": "<agent_key>",
      "pickup": "<pickup>",
      "dropoff": "<dropoff>",
      "date": "<date>",
      "time": "<time>",
      "pax": "<pax>",
      "name": "<name>",
      "phone": "<phone>",
      "email": "<email>",
      "terms_accepted": "<terms_accepted>"
    },
    "name": "request_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
paxYes
dateYesYYYY-MM-DD
nameYesThe customer's name: the person booking and paying (the passenger too, unless passenger_name is given)
timeYesHH:MM 24h
emailYesThe customer's email: the pay link, the confirmation and the receipt go here
notesNo
phoneYesThe customer's mobile
stopsNoOptional: stops on the way, in order, up to 4, each a street address or a hotel or venue name with its suburb; use the same stops as the get_quote you quoted. One way, this is the booking form's Multi-stop; on a return these are the stops on the way there (its Multi-stop return). The booking carries the stops and is made at the booking form's own total.
flightNoThe flight number they land on (e.g. QF512, JQ 430). Required for an airport pickup (Gold Coast, Brisbane or Ballina airport): without it nothing is booked, unless hire_car is true. "qf 512" and "Qantas 512" are booked as QF512; anything that is not a flight number is turned back.
pickupYes
dropoffYes
luggageNoOptional. Large suitcases (a pram or stroller counts as one). If left out, assumed to be what the chosen vehicle holds (never more than one per passenger).
vehicleNoVehicle choice; defaults to sedan. transporter = the 12-seater Transporter (up to 11 passengers), one vehicle for a group too big for one Carnival; for 9-11 people it takes up to 8 large bags, so a group with more luggage books 2-carnivals (two Kia Carnivals). There is no trailer. get_quote with pax gives the live seat, child-seat and luggage limits. Any other value is refused (accepted:false, "Unknown vehicle"), never booked as a different vehicle.
carry_onNoOptional. Carry-on bags.
hire_carNoTrue only when the customer is dropping off a hire car at the airport first, so there is no flight to land on: that airport pickup (or the way back from the airport) is then booked without a flight number, as the booking form's "Continue without a flight number" does. Never otherwise.
platformNoWhich channel this booking comes from (attribution)
seat_qtyNoChild seats by type, priced into the booking and pay link ($35 each): {seat index: quantity}. Indices follow the booking form list: 0 rear-facing 0-3yrs, 1 forward-facing 6mths-3yrs, 2 harnessed booster 3-6yrs, 3 booster with adult seatbelt 6yrs+.
agent_keyYesIssued gateway key
oversizedNoOptional. Surfboard, golf bag, bike box or similar (takes the space of three large bags, so sedans drop out). Not for a pram or stroller: count it in luggage and book the Carnival, not the sedan.
meet_greetNoOptional. Add the Brisbane Airport in-terminal meet and greet ($49). Gold Coast Airport pickups include it already.
child_seatsNoChild seats required ($35 each, supplied and fitted). Prefer seat_qty, which prices the seats into the booking and pay link.
heard_aboutNoOptional. How the customer heard about CGC, from their own answer: one of the booking form's 'How did you hear about us?' options, exactly as written (Google search; Google ad; Bing / Microsoft search; ChatGPT; Claude; Other AI assistant (Gemini, Copilot, etc.); Booked with you before; Friend or family recommended you; Hotel / accommodation recommended you; Facebook / Instagram / social media; Other). Leave out if they didn't say. Never guess, and never pick an AI option just because the booking comes through an AI.
heard_otherNoOptional. The customer's own words, up to 100 characters (e.g. 'saw your van at the airport'). The booking keeps them with an 'Other' answer.
return_dateNoOptional, YYYY-MM-DD. With return_time, books the return leg on the same reservation (5% return discount applies).
return_timeNoOptional, HH:MM 24h, in 5-minute steps. Required if return_date is given.
return_stopsNoOptional, only with return_date and return_time: stops on the way back, in order, up to 4, same rules as stops. Not copied from stops: leave out for none.
return_flightNoReturn trips whose way back starts at an airport: the flight number they land on for it (e.g. VA500). Required then, unless hire_car is true. Leave out otherwise.
return_pickupNoOptional, only with return_date and return_time: where the return trip picks up, if not the first trip's drop-off (in to one hotel, back from another). Defaults to the first trip reversed. With different return addresses each trip is priced at its own fare and the return discount comes off the cheaper trip, as on the booking form; use the same return_pickup and return_dropoff as the get_quote you quoted.
passenger_nameNoOptional, only when someone else is travelling (the customer is booking for them): the travelling passenger's name. Leave out when the customer is travelling.
return_dropoffNoOptional, only with return_date and return_time: where the return trip drops off, if not the first trip's pickup. Defaults to the first trip reversed.
terms_acceptedYesREQUIRED, must be true. Confirms the customer has been shown and has accepted the booking terms at https://cgctransfers.com.au/bookingtermsandconditions/ -- do not set this without an explicit yes from the customer.
passenger_emailNoOptional, with passenger_name: the travelling passenger's email, exactly as given. When the booking is paid they get their own confirmation there, without the price. A value that is not an email address is refused (accepted:false) and nothing is booked.
passenger_mobileNoOptional, with passenger_name: the travelling passenger's mobile. The driver contacts this number on the day, so ask for it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / vehicle / description
      Previous value: -"Vehicle choice; defaults to sedan. crafter = VW Crafter (up to 11 passengers), one van for a group too big for one Carnival; crafter-trailer = the same van towing a luggage trailer, for a big group with more luggage than the van takes (get_quote with pax gives the live seat, child-seat and luggage limits). Any other value is refused (accepted:false, \"Unknown vehicle\"), never booked as a different vehicle."New value: +"Vehicle choice; defaults to sedan. transporter = the 12-seater Transporter (up to 11 passengers), one vehicle for a group too big for one Carnival; for 9-11 people it takes up to 8 large bags, so a group with more luggage books 2-carnivals (two Kia Carnivals). There is no trailer. get_quote with pax gives the live seat, child-seat and luggage limits. Any other value is refused (accepted:false, \"Unknown vehicle\"), never booked as a different vehicle."
    • changedInput schema / properties / vehicle / enum
      Previous value: -[
      -  "sedan",
      -  "carnival",
      -  "carnival-rav",
      -  "2-carnivals",
      -  "crafter",
      -  "crafter-trailer"
      -]New value: +[
      +  "sedan",
      +  "carnival",
      +  "carnival-rav",
      +  "2-carnivals",
      +  "transporter"
      +]
  2. Changed3 schema fields changed
    • changedInput schema / properties / flight / description
      Previous value: -"The flight number they land on (e.g. QF512, JQ 430). Required for an airport pickup (Gold Coast, Brisbane or Ballina airport) - no exceptions: without it nothing is booked. \"qf 512\" is booked as QF512; anything that is not a flight number is turned back."New value: +"The flight number they land on (e.g. QF512, JQ 430). Required for an airport pickup (Gold Coast, Brisbane or Ballina airport): without it nothing is booked, unless hire_car is true. \"qf 512\" and \"Qantas 512\" are booked as QF512; anything that is not a flight number is turned back."
    • addedInput schema / properties / hire_car
      Added value: +{
      +  "description": "True only when the customer is dropping off a hire car at the airport first, so there is no flight to land on: that airport pickup (or the way back from the airport) is then booked without a flight number, as the booking form's \"Continue without a flight number\" does. Never otherwise.",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / return_flight / description
      Previous value: -"Return trips whose way back starts at an airport: the flight number they land on for it (e.g. VA500). Required then - no exceptions. Leave out otherwise."New value: +"Return trips whose way back starts at an airport: the flight number they land on for it (e.g. VA500). Required then, unless hire_car is true. Leave out otherwise."
  3. Changed6 schema fields changed
    • changedInput schema / properties / email / description
      Previous value: -"Passenger email (pay link goes here)"New value: +"The customer's email: the pay link, the confirmation and the receipt go here"
    • changedInput schema / properties / name / description
      Previous value: -"Passenger name"New value: +"The customer's name: the person booking and paying (the passenger too, unless passenger_name is given)"
    • addedInput schema / properties / passenger_email
      Added value: +{
      +  "description": "Optional, with passenger_name: the travelling passenger's email, exactly as given. When the booking is paid they get their own confirmation there, without the price. A value that is not an email address is refused (accepted:false) and nothing is booked.",
      +  "type": "string"
      +}
    • addedInput schema / properties / passenger_mobile
      Added value: +{
      +  "description": "Optional, with passenger_name: the travelling passenger's mobile. The driver contacts this number on the day, so ask for it.",
      +  "type": "string"
      +}
    • addedInput schema / properties / passenger_name
      Added value: +{
      +  "description": "Optional, only when someone else is travelling (the customer is booking for them): the travelling passenger's name. Leave out when the customer is travelling.",
      +  "type": "string"
      +}
    • changedInput schema / properties / phone / description
      Previous value: -"Passenger phone"New value: +"The customer's mobile"
  4. Changed2 schema fields changed
    • addedInput schema / properties / flight / description
      Added value: +"The flight number they land on (e.g. QF512, JQ 430). Required for an airport pickup (Gold Coast, Brisbane or Ballina airport) - no exceptions: without it nothing is booked. \"qf 512\" is booked as QF512; anything that is not a flight number is turned back."
    • addedInput schema / properties / return_flight
      Added value: +{
      +  "description": "Return trips whose way back starts at an airport: the flight number they land on for it (e.g. VA500). Required then - no exceptions. Leave out otherwise.",
      +  "type": "string"
      +}
  5. Changed2 schema fields changed
    • changedInput schema / properties / luggage / description
      Previous value: -"Optional. Large suitcases. If left out, assumed to be what the chosen vehicle holds (never more than one per passenger)."New value: +"Optional. Large suitcases (a pram or stroller counts as one). If left out, assumed to be what the chosen vehicle holds (never more than one per passenger)."
    • changedInput schema / properties / oversized / description
      Previous value: -"Optional. Surfboard, golf bag, bike box, full-size pram or similar (takes the space of three large bags, so sedans drop out)."New value: +"Optional. Surfboard, golf bag, bike box or similar (takes the space of three large bags, so sedans drop out). Not for a pram or stroller: count it in luggage and book the Carnival, not the sedan."
  6. Changed2 schema fields changed
    • addedInput schema / properties / heard_about
      Added value: +{
      +  "description": "Optional. How the customer heard about CGC, from their own answer: one of the booking form's 'How did you hear about us?' options, exactly as written (Google search; Google ad; Bing / Microsoft search; ChatGPT; Claude; Other AI assistant (Gemini, Copilot, etc.); Booked with you before; Friend or family recommended you; Hotel / accommodation recommended you; Facebook / Instagram / social media; Other). Leave out if they didn't say. Never guess, and never pick an AI option just because the booking comes through an AI.",
      +  "type": "string"
      +}
    • addedInput schema / properties / heard_other
      Added value: +{
      +  "description": "Optional. The customer's own words, up to 100 characters (e.g. 'saw your van at the airport'). The booking keeps them with an 'Other' answer.",
      +  "type": "string"
      +}
  7. Changed2 schema fields changed
    • addedInput schema / properties / return_stops
      Added value: +{
      +  "description": "Optional, only with return_date and return_time: stops on the way back, in order, up to 4, same rules as stops. Not copied from stops: leave out for none.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "maxItems": 4,
      +  "type": "array"
      +}
    • addedInput schema / properties / stops
      Added value: +{
      +  "description": "Optional: stops on the way, in order, up to 4, each a street address or a hotel or venue name with its suburb; use the same stops as the get_quote you quoted. One way, this is the booking form's Multi-stop; on a return these are the stops on the way there (its Multi-stop return). The booking carries the stops and is made at the booking form's own total.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "maxItems": 4,
      +  "type": "array"
      +}
  8. Changed2 schema fields changed
    • addedInput schema / properties / return_dropoff
      Added value: +{
      +  "description": "Optional, only with return_date and return_time: where the return trip drops off, if not the first trip's pickup. Defaults to the first trip reversed.",
      +  "type": "string"
      +}
    • addedInput schema / properties / return_pickup
      Added value: +{
      +  "description": "Optional, only with return_date and return_time: where the return trip picks up, if not the first trip's drop-off (in to one hotel, back from another). Defaults to the first trip reversed. With different return addresses each trip is priced at its own fare and the return discount comes off the cheaper trip, as on the booking form; use the same return_pickup and return_dropoff as the get_quote you quoted.",
      +  "type": "string"
      +}
  9. Changed1 schema field changed
    • changedInput schema / properties / vehicle / description
      Previous value: -"Vehicle choice; defaults to sedan. crafter = VW Crafter, one van for a group too big for one Carnival; crafter-trailer = the same van towing a luggage trailer, for a big group with more luggage than the van takes (get_quote with pax gives the live seat, child-seat and luggage limits). Any other value is refused (accepted:false, \"Unknown vehicle\"), never booked as a different vehicle."New value: +"Vehicle choice; defaults to sedan. crafter = VW Crafter (up to 11 passengers), one van for a group too big for one Carnival; crafter-trailer = the same van towing a luggage trailer, for a big group with more luggage than the van takes (get_quote with pax gives the live seat, child-seat and luggage limits). Any other value is refused (accepted:false, \"Unknown vehicle\"), never booked as a different vehicle."
  10. Changed2 schema fields changed
    • changedInput schema / properties / vehicle / description
      Previous value: -"Vehicle choice; defaults to sedan"New value: +"Vehicle choice; defaults to sedan. crafter = VW Crafter, one van for a group too big for one Carnival; crafter-trailer = the same van towing a luggage trailer, for a big group with more luggage than the van takes (get_quote with pax gives the live seat, child-seat and luggage limits). Any other value is refused (accepted:false, \"Unknown vehicle\"), never booked as a different vehicle."
    • changedInput schema / properties / vehicle / enum
      Previous value: -[
      -  "sedan",
      -  "carnival",
      -  "carnival-rav",
      -  "2-carnivals"
      -]New value: +[
      +  "sedan",
      +  "carnival",
      +  "carnival-rav",
      +  "2-carnivals",
      +  "crafter",
      +  "crafter-trailer"
      +]
  11. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnly=false, destructive=false), the description discloses the return contract (secure checkout_url handed to the customer), that no payment is ever taken through the tool, that closed days and blackout windows refuse with accepted:false before anything is lodged, and that an agent_key must be obtained from admin. That is unusually rich behavioral context for a mutation tool.

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 most important fact, the checkout_url handoff and no-payment rule, is front-loaded, and conditional rules follow in a workable order. Some length is unavoidable at 33 parameters, but the stops/return_stops paragraph restates much of the schema text and could be trimmed.

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 33-parameter, non-idempotent write tool with no output schema, the description covers the return value shape, failure signals (accepted:false variants), auth prerequisite, and the passenger-vs-customer confirmation split. Nothing an agent needs in order to call it correctly is 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 description coverage is already 88%, so the baseline is 3; the description nonetheless adds cross-parameter semantics the schema cannot express, such as return_stops not being copied from stops, return_flight only when the return leg starts at an airport, and passenger_* being omitted when the customer travels. Some fields (seat_qty, heard_about, vehicle) are only explained in the schema, so it is not fully additive.

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?

"Lodge a booking" gives a specific verb and resource, and the description immediately differentiates itself from the sibling get_quote by tying the same stops/quote to this call. An agent can tell this is the terminal write step after quoting, not another quote or availability check.

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 gives clear conditional guidance: flight required for airport pickups, hire_car as the sole exception, passenger_* fields only when someone else travels, and 'use the same stops/return_pickup as the get_quote you quoted'. It does not explicitly route to check_availability or state when not to call it, so it stops just short of a 5.

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