get_hotel_details
ClaudeFetch full details for a specific hotel by its local-hotel.com id (returned from search_hotels). Includes address, photos, amenities, reviews, and the booking URL. Links: give url and search_url exactly as returned, whole, because they carry the person's dates and guests after the #. Never build, shorten or change a link, and never give the home page in place of one; if no link was returned, say so.
get_hotel_rates
ClaudeGet the LIVE price of ONE hotel for ONE stay, checked just now: the lowest rate we are offered for these dates and guests, with checked_at and valid_until (a live price is only good until then). If the live check fails or a limit is reached you get NO price, never an old one, plus the hotel page url where the live price is shown. The hotel page re-checks the price before anyone books and its price is the one charged, so treat this as a check, not a promise. Call it for the one hotel the person picks, never in a loop over a list. Links: give url and search_url exactly as returned, whole, because they carry the person's dates and guests after the #. Never build, shorten or change a link, and never give the home page in place of one; if no link was returned, say so.
hotels_near_place
ClaudeList the bookable hotels closest to a landmark, attraction, airport or station we hold, with each hotel's STORED walking or car journey time to it (measured along real roads and paths, not live, and a car journey time ignores live traffic and says so). Ordered by the figure shown. A hotel we have not measured has no figure and none is guessed. Each hotel url is its page on local-hotel.com, where the live price is fetched and the user books. It also understands smaller landmarks, the names locals use for a place ("the Blinking Eye" is the Gateshead Millennium Bridge) and motorway junctions given as the road and the number ("M1 J25", "M25 junction 10"; a number alone is not enough). Walking and journey times are measured for major landmarks only: for those smaller places the answer says source: "straight_line" and gives each hotel's straight-line distance (as the crow flies), nearest first. Say it as a straight line and never turn it into a walking or journey time. When several places share a name it lists them with their towns: ask the person which town, then call again with "name, town". For a stadium or arena use hotels_near_venue. Links: give url and search_url exactly as returned, whole, because they carry the person's dates and guests after the #. Never build, shorten or change a link, and never give the home page in place of one; if no link was returned, say so.
hotels_near_venue
ClaudeList the bookable hotels closest to a stadium, arena, theatre or other venue, with each hotel's STORED walking or car journey time to it (measured along real roads and paths, not live, and a car journey time ignores live traffic and says so). Ordered by the figure shown. A hotel we have not measured has no figure and none is guessed. Take the venue from search_events (nearby_hotels.venue) or pass its name. Each hotel url is its page on local-hotel.com, where the live price is fetched and the user books. No prices here: call get_hotel_rates for the one hotel the person picks. Links: give url and search_url exactly as returned, whole, because they carry the person's dates and guests after the #. Never build, shorten or change a link, and never give the home page in place of one; if no link was returned, say so.
search_events
ClaudeSearch upcoming curated events (sport, music, festivals, air shows…) by name and/or city. Each result includes dates, venue, the event page URL, and where_to_stay — recommended hotel-search areas from the event's travel guide whose area strings can be passed directly to search_hotels as location. Use this to answer "where should I stay for [event]?" in one call: with a query, best_match holds the first match with its nearest hotels and their stored walking and car journey times (no prices; call get_hotel_rates for the one the person picks). We pick the best match and do not ask; the others follow. With a query, music results carry billing: "artist" when the stored performer is the query (these come first, soonest first), else "other" (a tribute act or any other listing with the name, soonest first). If no_shows_by is present, no show by the artist is listed: say so and never present a tribute act as the artist. Results can be limited to a window with from and to (YYYY-MM-DD). Each event carries its local_start (the venue's own clock) and suggested_stay, the dates its event page opens the hotel search on (null for a long run). The answer echoes what we understood and assumed (understood, assumed: two adults, one room unless told otherwise): say it back to the person. Each result also carries nearby_hotels: pass its venue (a slug) to hotels_near_venue for more hotels. When you pass a venue by name instead, add its city ("Allianz Stadium, London") or country: one name can be several venues. Links: give url and search_url exactly as returned, whole, because they carry the person's dates and guests after the #. Never build, shorten or change a link, and never give the home page in place of one; if no link was returned, say so.
search_hotels
ClaudeSearch hotels by TOWN OR CITY (for hotels near a named landmark, attraction, pier, station, airport or motorway junction call hotels_near_place; near a stadium, arena or theatre call hotels_near_venue: those answer with each hotel's stored journey time to it), with optional check-in/check-out dates and guest count. Returns the hotels we can book for a place in OUR ranking, the same order and set as the page for the place on local-hotel.com (hotels near the centre first, then by guest rating counting only hotels with enough reviews): keep that order, do not re-sort by rating, because a high rating from a handful of reviews is not a better hotel. Each hotel has rating with review_count (weigh them together), property_type (the supplier's own word: hotel, apartment and so on) and, when we have measured it, travel_to_centre (a stored walking or car journey time to the place's centre). State a distance ONLY from travel_to_centre; if it is absent we have not measured it, so do not estimate one (there are no coordinates here on purpose). query echoes the dates and guests as understood (dates_read_as, guests_read_as): confirm them with the person. Each url is the hotel's page with those dates and guests already set. It gives no prices: call get_hotel_rates for the one hotel the person picks. Links: give url and search_url exactly as returned, whole, because they carry the person's dates and guests after the #. Never build, shorten or change a link, and never give the home page in place of one; if no link was returned, say so.