Verified facts and direct-booking handoff for five Travellers Group hotels in regional Australia.
Scored across 12 tools
Each tool has a clearly distinct purpose: availability returns a pre-filled link, enquiries are separated by type, corporate info is separate from general property info, distances vs events vs rates vs room types vs town guide vs search vs recommendation. The only potential confusion is between create_enquiry and create_corporate_enquiry, but descriptions clarify the target audience. Overall, no ambiguity.
All tool names consistently follow a verb_noun pattern in snake_case (e.g., check_availability, get_distances, create_enquiry). The verbs are appropriate (check, create, get, recommend, search) and nouns clearly indicate the resource. No mixing of styles or vague verbs.
With 12 tools, the server is well-scoped for a hotel information and enquiry system. Each tool covers a distinct aspect of the domain without overlap or unnecessary bloat. The count is within the optimal range (3-15) for an MCP server.
The tool set covers core hotel information retrieval (property, rooms, rates, distances, events, town guide) and enquiry creation (general and corporate). However, there is no tool to complete a booking or confirm availability beyond a link. This is a minor gap; agents must hand off to the booking engine. Overall, the surface is mostly complete for its stated purpose.
Tier A handoff: returns a dated, pre-filled booking-engine link — LIVE availability and pricing are at that link. This tool never asserts that dates are available.
Inputs: check_in (required), property (required), check_out (required), adults, +1 more.
Corporate-account or group-booking enquiry, routed to the Travellers Group corporate team. Requires guest consent, as with create_enquiry.
Inputs: company (required), contact (required), context_summary (required), consent_confirmed (required).
Sends a booking enquiry to the property team (groups, crews, blocks, weekly stays, functions). Requires the guest’s explicit consent to pass their details and conversation context to the property.
Inputs: contact (required), property (required), context_summary (required), consent_confirmed (required), +2 more.
The Travellers Group corporate-account answer as data: one account, five properties, direct billing and consolidated invoicing.
Inputs: no named parameters.
Measured distances from a property (km, drive/walk minutes) to hospitals, mines, airports, venues, wineries. Fuzzy destination filter ('the zoo', 'hospital'). Serves published measured figures only.
Inputs: town, property, destination.
Verified events for a town. Serves only entries published with explicit dates — never extrapolates a date.
Inputs: town (required), to_date, from_date.
Indicative rate ranges from the published, commercially-signed rate module only — framed as indicative, never a quote. Where no figure is published, returns the booking link instead (never an estimate).
Inputs: property (required), room_type, stay_band.
Canonical entity record for a Travellers Group property: address, contacts, quick facts, policies, booking URL, parent entity.
Inputs: property (required).
Room catalogue for a property: occupancy, bedding, amenities, who-it-suits, booking deep link per room. traveller_context re-ranks honestly — it never invents inclusions.
Inputs: property (required), traveller_context.
Town knowledge layer: open-late, essentials, eat, with-kids, working-in, hospital-visitor, itineraries. Unbuilt topic returns 'not yet published' plus the town guide root.
Inputs: town (required), topic (required).
Honest matching across the Travellers portfolio. If no Travellers property suits the need, says so plainly and names the accommodation category that does. Never oversells. [Templates DRAFT pending G1.]
Inputs: need, town, context.
Search the published six-site Travellers Group corpus (guides, hubs, FAQs, pages). Returns ranked answer capsules (≤120 words) with canonical URLs.
Inputs: query (required), town, type, property.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Hotels that book direct: search, live-availability links, and AI-agent readiness checks.
Read-only facts on partner hotels: profile, rules, nearby places, official booking link.
Search and price stays on aura.travel, a global accommodation platform founded in Australia.
Read-only property facts, indicative availability, authorised booking links and guest-safe support.
Add one secure layer between your agents and this server.
