Skip to main content
Glama

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

Get booking form

get_booking_form
Read-only

The customer details needed to book a tour session or a rental (they vary by product), the booking terms the customer agrees to when booking, and the total price.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_booking_form"
  }
}

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.
session_idNoTour session

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value beyond them by disclosing the three content groups returned (customer details, terms, total price) and warning that fields vary by product, which is important since no output schema exists. It still omits whether a session_id or rental block is needed to get a meaningful form, and says nothing about validation or failure behavior.

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?

A single sentence with three enumerated content groups and a parenthetical qualifier; there is no padding or repetition. It is front-loaded on what matters, though the sentence reads as a fragment without a leading verb.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter tool with a nested rental object and no output schema, the description does cover the return contents in outline, which is the biggest gap it could have filled. However it leaves unclear which parameter combinations are required to produce a usable form and gives no workflow context connecting it to check_availability or create_booking.

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 86%, so the nested rental object, guest_types override, and age-band semantics are already documented in the schema and the baseline is 3. The description contributes nothing parameter-specific, and notably does not explain the interaction between date/session_id and the rental block that the schema leaves implicit.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a noun phrase listing what the form contains ('customer details', 'booking terms', 'total price') rather than stating an action verb, so the retrieval behavior is only implied by the name. The contents are specific and the note that they 'vary by product' is genuinely informative, but it never explicitly says it returns a form for a proposed booking or how that differs from the other read tools in the family.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance at all: nothing says to call this before create_booking, after check_availability, or how it relates to list_tours/list_rentals which supply session_id and item_id. The agent must infer the ordering of the booking workflow entirely.

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