Skip to main content
Glama

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

Check tour availability

check_availability
Read-only

Live places and prices for one tour on one date, straight from the booking system. Returns each session that can be booked, places left, total price for the group, the guest types it takes, and a booking link the customer can open to book themselves.

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": {
      "tour": "<tour>",
      "date": "<date>"
    },
    "name": "check_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesYYYY-MM-DD, Noosa time
tourYesTour key, as listed by list_tours
adultsNoAdults (on kayak tours: anyone 13 and over)
guestsNoOptional: exact counts by the guest_types keys that check_availability returns. Overrides adults/children/infants.
infantsNoInfants and toddlers aged 3 and under (kayak tours)
childrenNoChildren (kayak tours: ages 4 to 12). Bike tours have no child rate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / tour / description
      Previous value: -"Tour key from list_tours"New value: +"Tour key, as listed by list_tours"
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the description's job is to add more, which it does by disclosing the exact return payload: bookable sessions, places left, group total price, accepted guest types, and a customer-facing booking link. That is real value given there is no output schema. It stops short of covering cache/freshness timing or sold-out behavior, keeping it below 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.

Conciseness4/5

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

Two sentences, front-loaded with purpose before the return inventory, with essentially no filler. The second sentence is a long comma-separated list, which is dense but each item is load-bearing information an agent cannot get from the schema.

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 read-only availability lookup with six parameters and no output schema, this covers the essentials: what is queried, what comes back, and that the data is live. The remaining gap is edge-case behavior (no availability, currency, caching window), which an agent would likely need but can often discover at call time.

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 100%, so the baseline is 3 and the schema already documents date format, tour key, adults/children/infants, and the guests override. The description adds only marginal meaning by noting the returned "guest types it takes" relate to the guests parameter. No new syntax or semantics are introduced.

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?

"Live places and prices for one tour on one date" pairs a specific resource (tour availability) with concrete scope (one tour, one date) and explicitly sources it from the booking system. An agent can immediately distinguish this from check_rental_availability and list_tours because the resource and intent are named, not implied.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the mention of a booking link and the required tour/date pair suggest this is the pre-booking lookup step, but the description never says when to prefer it over create_booking or get_booking_form. There are no exclusions, no prerequisites, and no note about what to do when no sessions are returned.

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