Skip to main content
Glama

Noosa tours and bike hire (By Earth and Ocean, Bike On)

Hold a booking (unpaid, 30 minutes)

create_booking

Book a tour session or Bike On rental for the customer. The booking is made unpaid and holds the places for 30 minutes; the customer must pay with the payment link returned, on our secure booking page (no card details are ever taken here). Unpaid bookings are cancelled automatically. Needs the customer's confirmation of the details and their agreement to the booking terms.

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": {
      "customer": "<customer>",
      "customer_agreed_to_terms": "<customer_agreed_to_terms>",
      "customer_confirmed_details": "<customer_confirmed_details>"
    },
    "name": "create_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNo
adultsNoAdults (on kayak tours: anyone 13 and over)
guestsNoOptional: exact counts by the guest_types keys that check_availability returns. Overrides adults/children/infants.
rentalNoFor Bike On bike rentals instead of a tour.
infantsNoInfants and toddlers aged 3 and under (kayak tours)
childrenNoChildren (kayak tours: ages 4 to 12). Bike tours have no child rate.
customerYesField values by key from get_booking_form (customer_name, customer_email, customer_phone and any others it requires)
session_idNoTour session (or give rental instead)
customer_agreed_to_termsYesTrue only if the customer has read and agreed to the booking terms
customer_confirmed_detailsYesTrue only if the customer confirmed tour, date, time, numbers and price

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that the hold lasts 30 minutes, that unpaid bookings are cancelled automatically, that no card details are taken, and that a payment link is returned for the customer to pay on the secure page. It also explains the two consent booleans as real-world gating conditions, which the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false) alone cannot convey.

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?

Three sentences, front-loaded with the action and the most decision-relevant fact (unpaid 30-minute hold), followed by consequences and prerequisites. No filler or restatement of the tool name.

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 10-parameter, nested-object mutation tool with no output schema, the description covers the return value (payment link), the hold/expiry lifecycle, and the consent preconditions. It leaves open what happens on contention (spots taken between availability check and booking) and any error/retry semantics.

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 description coverage is 90%, so nearly every parameter (guest breakdowns, session_id vs rental, list_rentals item_ids, get_booking_form field keys) is already documented in the schema. The description only reinforces the two consent booleans and the confirmation requirement, adding little that the schema does not already say.

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?

States a specific verb and resource ('Book a tour session or Bike On rental') and clarifies that what is created is an unpaid 30-minute hold, not a paid booking. This cleanly separates it from the read-only siblings (check_availability, list_tours, list_rentals), though no sibling is named explicitly.

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?

Gives concrete preconditions: the customer must confirm the details and agree to the terms, and the customer object must come from get_booking_form keys. It stops short of stating the expected call order (e.g. check availability first, then create) or what to do if the session is no longer available.

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