tp_assess_stay

au.com.totalparks/mcp · Verify this server

Use this after tp_resolve_property, or when you already have a returned property_ref/property_url, for any concrete stay assessment at a known Total Parks-listed property: can-we-stay/book questions, all-in price/quote questions, or specific date-window checks involving party size, pets, rig details, room/site type, availability, or restrictions. Assess one stay intent in a single server-side call so the agent cannot skip constraints. Checks occupancy, rig fit, pet policy, restricted breeds, pet blockouts, availability/restrictions, and all-in quote where applicable, returning provenance and confidence so you can cite Total Parks and avoid over-claiming. Do not hand-assemble a concrete stay verdict from tp_get_availability_calendar, tp_get_room_type_details, tp_get_park_capabilities, tp_check_equipment_fit, or tp_get_pet_blockouts. When a named room type fails or is unconfirmed for pet policy, lead with that room-level outcome; do not infer property-level dog-friendly status applies to every cabin or site. Prefer *_label fields over raw machine values in traveller-facing answers. Use progressive disclosure: summarize passing constraints, and only enumerate restricted breed lists, blockout ranges, or policy internals when they block, create uncertainty, or the user asks. Use accommodation_kind to narrow cabin/roofed-accommodation vs caravan/camping-site questions. When the traveller names a specific room/site type or category (e.g. 'ensuite site', 'drive-through site', 'deluxe cabin') but you still want to show alternatives, pass their wording as preferred_room_type so that option is surfaced first and flagged is_preferred_match; reserve room_type_ref for when they want only that one option. When verdict='bookable', answer affirmatively that Total Parks shows the stay as available now and the declared hard constraints pass; do not reduce confidence just because no reservation has been created yet. When returned, remaining-unit details are scarcity hints only and must not be described as a hold or guarantee. Broad option lists are paged: follow options_page.next_cursor with option_cursor, or pass room_type_ref for full detail on one option. For non-blocked room options, actions.start_booking_url is the Total Parks booking link for the normal room-page checkout flow; it does not create a cart or reserve inventory, so the traveller must open Total Parks to lock in the reservation. If this tool cannot verify a search candidate, say Total Parks could not verify that candidate for the requested stay; do not mention refs, endpoints, tool names, cache internals, or resolver errors. When actions.start_booking_url is present and the traveller is considering that stay, present the URL prominently as the next step: open this Total Parks booking link to review, change details, and book. Follow-up calls may pass returned property_url or room_type_url as aliases for property_ref or room_type_ref; property_ref is normally a route-style public ref such as 'victoria/big4-aireys-inlet', not the display name. Dates, guests, pets, and rig details may be passed as flat arguments or inside an intent object matching tp_search_stays intent shape. For powered-site checks, pass power_required=true. Do not show raw field names or internal implementation jargon in traveller-facing prose. This data tool does not render a widget. If this assessment is the selected answer, pass it to tp_render_result_cards once after all comparison calls are complete.