Skip to main content
Glama

Camping Australia

by au.com.trip-planner

Complete booking checkout

bk_cart_checkout
Destructive

Finalise the Bookeasy cart and get the SINGLE checkout URL the user uses to complete payment. TWO-STEP, human-in-the-loop:

  1. Call WITHOUT confirm — this returns the booking summary + total price and NO payment link. Show the traveller the full summary (property, dates, guests, total) and ask them to confirm.

  2. Only after they EXPLICITLY agree, call again with confirm=true to get the secure payment link. Never set confirm=true yourself without the traveller's clear yes. Payment happens on Bookeasy's page — never tell the user the booking is 'confirmed' from chat; it's pending until they pay. Only call once the cart is ready (no pending questions) and bk_cart_guest has set the lead guest. The checkout URL covers the whole cart.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoSet true ONLY after the traveller has seen the full summary + total and explicitly agreed. Without it, the payment link is withheld and only the summary is returned.
session_keyYesThe cart session key

TDQS

A4.8/5.0
Behavior5/5

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

Despite annotations marking destructiveHint=true and readOnlyHint=false, the description adds substantial behavioral context: the two-step confirmation flow, that no payment link is issued without confirm, payments occur on Bookeasy's page, and the booking is pending until paid. This goes well beyond the annotations.

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 description is longer than average but tightly structured with numbered steps and bolded key instructions. Every sentence contributes meaningful guidance, though a few phrases could be trimmed without losing clarity.

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?

With no output schema, the description compensates by explaining what each call returns (summary vs payment link), when to call, and what not to do. It fully covers the human-in-the-loop complexity and integrates prerequisites, making it complete for an agent to invoke correctly.

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% and the confirm parameter description already explains withholding the link. The tool description adds value by clarifying that the first call returns summary+total and the second call returns the secure link, deepening understanding of how the parameters drive behavior.

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 opens with a specific verb ('Finalise') and resource ('Bookeasy cart'), clearly stating the tool returns a SINGLE checkout URL. It distinguishes this from sibling cart tools like bk_cart_add and bk_cart_promo by focusing on finalization and payment, not modification.

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?

Provides explicit two-step usage instructions with a critical human-in-the-loop rule: call without confirm first, then only with confirm=true after the traveller explicitly agrees. It also states preconditions ('cart is ready', lead guest set) and warns against using when pending questions, making alternatives and timing clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Camping Australia toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

Each tool targets a distinct operation: bk_* for Bookeasy booking workflows (add, checkout, guest, promo, search operators/content), get_* for retrieval, search_* for different domains (campsites, campervans, products), and find_nearest_toilets and recommend_gear for specific niche queries. No significant overlap.

Naming Consistency5/5

Naming follows a consistent pattern: bk_ prefix for Bookeasy tools, then verb_noun (e.g., bk_cart_add, bk_search_operators). Non-bk tools use get_ or search_ prefixes. All snake_case, predictable and clear.

Tool Count5/5

18 tools cover a broad scope (accommodation search, campervan rental, public toilets, weather, gear, products, and full booking lifecycle) without bloat. Each tool earns its place; the count is well-scoped for the domain.

Completeness4/5

The tool set covers most user needs: listing, searching, booking, weather, gear, product sales. Minor gaps (e.g., no tool for cancelling/viewing past bookings) but these are likely handled externally via the booking platform. The core workflows are well-supported.

Resources