HotelME

Ordinary hotel comparison; for ふっこう割 use search_campaign_availability first. Use this when comparing 2–3 returned public hotels in input order; no Metro login. For ふっこう割/official direct campaigns, use search_campaign_availability if listed. Never substitute this tool's ordinary OTA prices or links as campaign offers. Unavailable/zero/unverified campaign results stay unconfirmed; do not infer discounts. Ordinary OTA searches remain supported when requested separately as non-campaign. Follow explicit campaign_period_guidance continuations with the same conditions; enforce required_result_prefecture and label ふっこう割対象外・通常料金. Dates are optional for aggregate review comparisons; do not block them on dates. Compare the returned hotels in one call rather than parallel per-hotel detail calls. Preserve unknowns. Theme counts overlap, not unique guests. Display date-prefilled URLs verbatim; observed price is not a guaranteed offer at the URL. Dates and party must not be altered to bypass unsupported conditions. No reservations or live quotes. State the actual displayed hotel count. Include each displayed price's OTA source, 参考料金・確定料金ではありません label and differing price bases, not just the cheapest amount. Keep observation/acquisition/check dates and times internal, not in user answers. Repeat source and reference-price labels in each follow-up comparison or changed-date answer, even if already stated earlier. Use table columns or a note explicitly bound to the relevant hotel/date; a shared note is valid only when those provenance values match. Compare food using returned fine-grained meal aggregates and their positive/negative counts, not an invented single food score. Identify specific supported strengths and concerns; missing subthemes are unknown, and mentions overlap rather than count guests. Never reconstruct individual reviews or infer a verified menu, dish or facility. Keep general travel-preparation tips separate from verified facts about each hotel. Booking answers: distinguish matching hotel candidates, reference prices and currently bookable offers. HotelME does not verify live booking availability. A hotel listing or a date-prefilled URL is not evidence of a bookable room. Link labels should invite checking availability, not promise a reservation. Check the returned availability for the SAME hotel, OTA, dates and party before associating a price with a link. A price on another OTA does not establish Booking.com availability. For a source marked observed_sold_out, state no availability was confirmed there and do not promote its link as an available offer. Do not display a booking URL suppressed for that source's sold-out date or recreate it from previous turns. Unknown/stale/missing is not sold out. Never infer exact-date availability or sell-out from overlapping, longer, shorter or nearby date ranges. Daily minima across different providers or plans do not establish a continuous stay. If the user reports no rooms at the booking site, acknowledge that the reference result is not a live quote; verify the exact hotel, OTA, dates and party in the supplied result and link. Do not override their current observation with cached data, claim a fresh live check, or repeat the same failed candidate as bookable. When searching alternatives, preserve ALL dates, party, destination, budget and required accommodation type; ask before changing them. If no qualifying candidate is verified, say so first. Do not fill the requested count with unverified Web suggestions, general starting rates, over-budget properties or ordinary hotels when ryokans were required. Offer a specific condition change for the user's approval instead. Separately requested external research must be attributed to its own source and clearly marked unverified for the requested stay; it is not a HotelME match. Translate diagnostics into traveler language; never copy total_matches, price_unverified, observed_sold_out or other field names into prose or tables. Say '条件に合う参考料金を確認できた ホテル' for a priced result count, '指定日の参考料金を確認できません' for unverified prices, and 'この予約サイトでは指定条件の空室なし' only for explicit per-site sold-out evidence. Use '参考料金' rather than 観測価格/観測料金, and '料金を確認できたホテル' rather than 監視対象施設. Do not show acquisition timestamps. A zero priced-result count is not proof all hotels are full. If explicit sold-out evidence is present, offer the previous or next check-in date as an OPTIONAL new search, with the same nights/party/budget/themes. Unless those exact alternative stays were already returned, say those dates have not been searched; do not claim vacancies or change dates until the user chooses. If no search ran, say 未検索・件数未判定, never 0件.

Hotel details only; for ふっこう割 use search_campaign_availability first. Use this when reading aggregate review evidence for one returned public hotel. For ふっこう割/official direct campaigns, use search_campaign_availability if listed. Never substitute this tool's ordinary OTA prices or links as campaign offers. Unavailable/zero/unverified campaign results stay unconfirmed; do not infer discounts. Ordinary OTA searches remain supported when requested separately as non-campaign. Follow explicit campaign_period_guidance continuations with the same conditions; enforce required_result_prefecture and label ふっこう割対象外・通常料金. Dates are optional for aggregate analysis; never expose raw guest text. Reuse an existing result if it already contains the requested evidence, prices or links. Pass exact known dates/party for booking searches; never return a hotel front page instead. dates_required applies only to booking links, not aggregate analysis; ask dates only if links or prices are requested. Missing links never permit guessing. Show each price's source and 参考料金・確定料金ではありません (reference price, not a live quote), not observation/check timestamps. Confirm final prices and availability on the booking site. For food reviews, explain returned fine-grained meal themes with positive/negative counts and sample limitations: e.g. variety, local ingredients or service ONLY when that subtheme is returned. Distinguish supported strengths, concerns and unknowns. These counts concern overlapping theme mentions, not unique guests. Never invent dishes, quotes, one-review paraphrases, verified menus or guaranteed experiences. Reuse existing evidence; request details only if the needed aggregate evidence is missing. Label general hiking/trip preparation separately as 旅行の準備（一般情報）, not hotel facts. No Metro login. Cannot provide unverified amenities, walk times, photos or private reports. Cannot bypass unsupported-party limits from another tool. Booking answers: distinguish matching hotel candidates, reference prices and currently bookable offers. HotelME does not verify live booking availability. A hotel listing or a date-prefilled URL is not evidence of a bookable room. Link labels should invite checking availability, not promise a reservation. Check the returned availability for the SAME hotel, OTA, dates and party before associating a price with a link. A price on another OTA does not establish Booking.com availability. For a source marked observed_sold_out, state no availability was confirmed there and do not promote its link as an available offer. Do not display a booking URL suppressed for that source's sold-out date or recreate it from previous turns. Unknown/stale/missing is not sold out. Never infer exact-date availability or sell-out from overlapping, longer, shorter or nearby date ranges. Daily minima across different providers or plans do not establish a continuous stay. If the user reports no rooms at the booking site, acknowledge that the reference result is not a live quote; verify the exact hotel, OTA, dates and party in the supplied result and link. Do not override their current observation with cached data, claim a fresh live check, or repeat the same failed candidate as bookable. When searching alternatives, preserve ALL dates, party, destination, budget and required accommodation type; ask before changing them. If no qualifying candidate is verified, say so first. Do not fill the requested count with unverified Web suggestions, general starting rates, over-budget properties or ordinary hotels when ryokans were required. Offer a specific condition change for the user's approval instead. Separately requested external research must be attributed to its own source and clearly marked unverified for the requested stay; it is not a HotelME match. Translate diagnostics into traveler language; never copy total_matches, price_unverified, observed_sold_out or other field names into prose or tables. Say '条件に合う参考料金を確認できた ホテル' for a priced result count, '指定日の参考料金を確認できません' for unverified prices, and 'この予約サイトでは指定条件の空室なし' only for explicit per-site sold-out evidence. Use '参考料金' rather than 観測価格/観測料金, and '料金を確認できたホテル' rather than 監視対象施設. Do not show acquisition timestamps. A zero priced-result count is not proof all hotels are full. If explicit sold-out evidence is present, offer the previous or next check-in date as an OPTIONAL new search, with the same nights/party/budget/themes. Unless those exact alternative stays were already returned, say those dates have not been searched; do not claim vacancies or change dates until the user chooses. If no search ran, say 未検索・件数未判定, never 0件.

Ordinary OTA prices only; for ふっこう割 use search_campaign_availability first. Use this when comparing cached daily prices for 1–3 hotels across 1–14 nights. For ふっこう割/official direct campaigns, use search_campaign_availability if listed. Never substitute this tool's ordinary OTA prices or links as campaign offers. Unavailable/zero/unverified campaign results stay unconfirmed; do not infer discounts. Ordinary OTA searches remain supported when requested separately as non-campaign. Dates are required for this calendar tool; not for review-only discovery. No login. Check-out is exclusive, within today JST to six calendar months. The entire stay must fit returned supported_window: start <= check_in < check_out <= end. Do not predict future data readiness from check-in alone. Only 2 adults, 1 room, no children. Request a flexible one-night range once, not per day. Compare hotel×date combinations, retaining repeated hotels unless unique hotels were asked. Unknown/stale/uncollected is not zero or sold out. Source sell-out is not hotel-wide fullness. Observed prices are not live quotes, same-plan stay totals or tax guarantees. Use source_availability_labels per OTA/date, combining observations with source_availability_gaps. For each source_availability_sources entry missing from both, use source_availability_default (not_collected). Never infer sold-out from absence. Match source aliases: じゃらん=Jalan.net, 楽天トラベル=Rakuten.co.jp. Keep unknown, no usable observation and expired information distinct. Expired information is historical; never show its price. Missing source records do not establish a failed fetch or no previous collection. Show per-source availability status without timestamps. Include each displayed price's OTA source and 参考料金・確定料金ではありません label. Keep observation/acquisition/check dates and times internal, not in user answers. Confirm final prices and availability on the booking site. Show supplied booking URLs verbatim using normal clickable Markdown links, not button-only controls; never invent missing links. Booking answers: distinguish matching hotel candidates, reference prices and currently bookable offers. HotelME does not verify live booking availability. A hotel listing or a date-prefilled URL is not evidence of a bookable room. Link labels should invite checking availability, not promise a reservation. Check the returned availability for the SAME hotel, OTA, dates and party before associating a price with a link. A price on another OTA does not establish Booking.com availability. For a source marked observed_sold_out, state no availability was confirmed there and do not promote its link as an available offer. Do not display a booking URL suppressed for that source's sold-out date or recreate it from previous turns. Unknown/stale/missing is not sold out. Never infer exact-date availability or sell-out from overlapping, longer, shorter or nearby date ranges. Daily minima across different providers or plans do not establish a continuous stay. If the user reports no rooms at the booking site, acknowledge that the reference result is not a live quote; verify the exact hotel, OTA, dates and party in the supplied result and link. Do not override their current observation with cached data, claim a fresh live check, or repeat the same failed candidate as bookable. When searching alternatives, preserve ALL dates, party, destination, budget and required accommodation type; ask before changing them. If no qualifying candidate is verified, say so first. Do not fill the requested count with unverified Web suggestions, general starting rates, over-budget properties or ordinary hotels when ryokans were required. Offer a specific condition change for the user's approval instead. Separately requested external research must be attributed to its own source and clearly marked unverified for the requested stay; it is not a HotelME match. Translate diagnostics into traveler language; never copy total_matches, price_unverified, observed_sold_out or other field names into prose or tables. Say '条件に合う参考料金を確認できた ホテル' for a priced result count, '指定日の参考料金を確認できません' for unverified prices, and 'この予約サイトでは指定条件の空室なし' only for explicit per-site sold-out evidence. Use '参考料金' rather than 観測価格/観測料金, and '料金を確認できたホテル' rather than 監視対象施設. Do not show acquisition timestamps. A zero priced-result count is not proof all hotels are full. If explicit sold-out evidence is present, offer the previous or next check-in date as an OPTIONAL new search, with the same nights/party/budget/themes. Unless those exact alternative stays were already returned, say those dates have not been searched; do not claim vacancies or change dates until the user chooses. If no search ran, say 未検索・件数未判定, never 0件.

Use this when mapping a review preference to published theme IDs; no Metro login. For a hotel search with an ambiguous destination (e.g. 港区/中央区/北区), first ask which prefecture/city unless the user's explicit context resolves it; never assume Tokyo. A request for 港区 alone needs clarification (Tokyo, Osaka or Nagoya); a theme, language, device location or a popular hotel cannot resolve that ambiguity. This takes priority over choosing breakfast subtypes. Standalone theme browsing needs no destination. Discover once per keyword and reuse IDs; dates are not needed. General breakfast is not buffet; onsen does not imply a private bath. Review mentions are aggregate analysis, not verified hotel facilities or individual guest text. Keyword matches are alternative topics, not a list of jointly required filters. For good breakfast, use a returned general breakfast theme when available. If only narrower subtypes are returned, ask one brief clarification before searching. Do not select buffet or another subtype without the user's consent. For food details, discover relevant fine-grained meal themes once and reuse their IDs. Explain only returned subthemes, not invented dish names or guest quotations. Related subthemes are comparison dimensions, not automatically AND requirements.

Ordinary hotel search only; for ふっこう割 use search_campaign_availability first. Use this for non-campaign hotel names, destinations or aggregate review themes. For ふっこう割/official direct campaigns, use search_campaign_availability if listed. If unavailable, zero or unverified, explain that campaign availability is unconfirmed. Never substitute this tool's ordinary OTA prices or links as campaign offers, or calculate campaign discounts from them. Ordinary OTA searches remain supported when requested separately; label those offers non-campaign and preserve the user's choice. Also follow an explicit normal_price_search continuation from campaign_period_guidance after explaining official ineligibility. Keep the original conditions and label prices ふっこう割対象外・通常料金. A cache coverage gap alone never authorizes this continuation. Resolve ambiguous destinations (e.g. 港区/中央区/北区) from explicit user context or ask which prefecture/city before looking up themes or asking about subtypes. Never assume Tokyo or another city; do not invent a prefecture. Example: 港区で眺めのいいホテル needs a city clarification, not a Tokyo search. Offer 東京都港区, 大阪市港区 and 名古屋市港区, not just Tokyo and Osaka. 大阪市港区で眺めのいいホテル is explicit: preserve Osaka, never substitute Tokyo. For bare 品川 ask 品川駅周辺 or 品川区. Station areas and city/ward boundaries differ. An administrative-area match never verifies distance from a station. Pass the original station request (e.g. 金沢駅徒歩圏) rather than stopping for unsupported walking distance. If the service returns a city-wide reference notice, explain that scope BEFORE the candidates and that walking distance is unverified. Do not label those candidates station-near or verified matches to every condition. Keep dates, party, budget, hotel name and required themes. Never silently rewrite 博多駅周辺 as 博多区. For unresolved or conflicting places, ask before broadening; never invent a city. Dates are optional for hotel discovery and aggregate review analysis. Run these searches without dates; do not require a stay date just to find breakfast themes. Ask dates only when prices, budget filtering or date-prefilled booking links are requested. Metro registration/login is not required. Return up to 5 hotels. Pass all known dates, party, themes and budget together. Every selected theme must match: include only explicitly required themes. For good breakfast, use a returned general breakfast theme when available. If only narrower subtypes are returned, ask one brief clarification before searching; do not select buffet without consent. Related themes can be comparison dimensions, not mandatory search filters. For meal quality, use returned fine-grained aggregate themes to explain specific strengths and concerns. Missing themes are unknown, not proof of poor food or no meals. Separate general trip-purpose advice (e.g. hiking preparation) as 旅行の準備（一般情報）; it does not verify this hotel's trail proximity, transport, equipment or facilities. Put the requested city/ward in location and hotel/chain name in hotel_name; do not merge them. A prefecture alone does not narrow to its similarly named city. Keep branch/building/sub-brand words in hotel_name. Location is not a meal preference or walking-distance guarantee. Japanese and English city forms are accepted. For explicit exclusions, pass prior returned IDs in exclude_hotel_ids or the user's named hotel/brand keywords in exclude_hotel_names. Exclusions run before ranking and budget selection, so eligible replacements can fill the requested limit. Preserve exclusions on follow-up searches along with all other conditions. Name exclusions are not a corporate ownership or entire hotel-group guarantee: do not infer unnamed affiliated brands. Clarify a requested corporate group if its brands are unknown. Names allow width/kana/separator variants and curated aliases, not arbitrary typos. If search_diagnostic is returned, explain its reason. name_suggestions are only possible identities, NOT matching recommendations; ask which hotel was intended. name_search_limited is an inconclusive bounded search, not proof that a hotel does not exist or lacks review evidence. Missing names can reflect catalog coverage or a different registered name. Never replace an unavailable named branch with a similarly named sister hotel or claim it is that same property. They have no verified theme/price match. After confirmation, retry recommend_hotels with the confirmed name and ALL original place, branch, theme, date, party and budget conditions. Do not bypass these filters by fetching suggestion IDs through details. A limited/unavailable name lookup is not proof that the hotel is absent. Zero results do not prove missing data, poor reviews or sell-out; clarify the name or city without dropping other conditions. Show returned registered names. Ask for destination when a vague trip is unresolved; do not substitute national leaders. No photo URLs are returned. Prefer text and clickable links; omit image carousels and unavailable-image placeholders. External citations must match the exact branch and location, not merely the same brand; omit unverified factual claims. Report the actual number of hotels displayed, not the requested limit. Do not count name_suggestions or excluded locations as matches. If fewer match, state that count. Review-count order is not overall quality. Nightly and whole-stay budget caps are JPY per room, not per person; never divide total budget by nights. Both caps apply if set. Budget filtering must occur before top-k; unknown/stale prices cannot satisfy a cap. A sum of observed nightly minima is not a same-plan quote or live availability. Prices and date-prefilled booking searches support 2 adults, 1 room, no children only. Never change party/dates, silently relax conditions or invent prices/links. Show supplied booking URLs verbatim, including dates. Use normal clickable Markdown links, not button-only controls. No separate lookup for the same links or prices already returned here. An unsupported condition requires asking the user before continuing, not a retry through another tool. No booking/payment actions. Include each displayed price's OTA source and 参考料金・確定料金ではありません label. Keep observation/acquisition/check dates and times internal, not in user answers. Show per-source availability status without timestamps. Stale information is historical; never show expired prices. For not_collected, do not invent a failed-fetch reason or claim it was never collected. Search one condition set at a time and reuse returned results; do not fan out repeated searches. Booking answers: distinguish matching hotel candidates, reference prices and currently bookable offers. HotelME does not verify live booking availability. A hotel listing or a date-prefilled URL is not evidence of a bookable room. Link labels should invite checking availability, not promise a reservation. Check the returned availability for the SAME hotel, OTA, dates and party before associating a price with a link. A price on another OTA does not establish Booking.com availability. For a source marked observed_sold_out, state no availability was confirmed there and do not promote its link as an available offer. Do not display a booking URL suppressed for that source's sold-out date or recreate it from previous turns. Unknown/stale/missing is not sold out. Never infer exact-date availability or sell-out from overlapping, longer, shorter or nearby date ranges. Daily minima across different providers or plans do not establish a continuous stay. If the user reports no rooms at the booking site, acknowledge that the reference result is not a live quote; verify the exact hotel, OTA, dates and party in the supplied result and link. Do not override their current observation with cached data, claim a fresh live check, or repeat the same failed candidate as bookable. When searching alternatives, preserve ALL dates, party, destination, budget and required accommodation type; ask before changing them. If no qualifying candidate is verified, say so first. Do not fill the requested count with unverified Web suggestions, general starting rates, over-budget properties or ordinary hotels when ryokans were required. Offer a specific condition change for the user's approval instead. Separately requested external research must be attributed to its own source and clearly marked unverified for the requested stay; it is not a HotelME match. Translate diagnostics into traveler language; never copy total_matches, price_unverified, observed_sold_out or other field names into prose or tables. Say '条件に合う参考料金を確認できた ホテル' for a priced result count, '指定日の参考料金を確認できません' for unverified prices, and 'この予約サイトでは指定条件の空室なし' only for explicit per-site sold-out evidence. Use '参考料金' rather than 観測価格/観測料金, and '料金を確認できたホテル' rather than 監視対象施設. Do not show acquisition timestamps. A zero priced-result count is not proof all hotels are full. If explicit sold-out evidence is present, offer the previous or next check-in date as an OPTIONAL new search, with the same nights/party/budget/themes. Unless those exact alternative stays were already returned, say those dates have not been searched; do not claim vacancies or change dates until the user chooses. If no search ran, say 未検索・件数未判定, never 0件.

Ask only missing hotel-search conditions, with choices and optional date inputs. Use BEFORE hotel/theme searches if destination is missing or ambiguous, or dates or party are missing for prices, budgets, booking links or a campaign. Never invent dates, a destination or adult counts. Ordinary form defaults: if checkout is omitted, use the given check-in plus the specified nights, or one night when nights are omitted. Unspecified children use the adult-only scope (children=0) without asking a child count. Preserve explicit children and date values; do not present adult-only results as matching a family. Campaign exception: unspecified children uses the fixed adults-only scope (children=0), without a separate consent question. Explicit children>0 does not stop a campaign search: keep that count in conditions and continue as an adults-only reference, without asking consent or a child count/age. Preserve the returned adult-reference notice in the answer and subsequent tool call. Campaign rooms>1 also permits a one-room reference without another approval question. Keep original rooms (1–4) in conditions and subsequent campaign arguments; never divide or reduce the adult count. Retain the single-room notice: multiple-room availability and total price are unconfirmed. This exception does not apply to OTA search. Child prices and availability/total for the whole family are unverified; users must add children on the official booking site. Never count children as adults or present adult-only prices/links as matching the whole family. Explicit unsupported ordinary party conditions remain unchanged and are not converted into a supported family search. Include context confirmed for the current search intent; do not ask those questions again. Campaign price bounds/sort/scope/luxury band are retained in conditions; pass them unchanged to search_campaign_availability after missing details are answered. On an explicit switch from ordinary search to ふっこう割, if no area is specified for the new campaign request, do not carry forward a prior non-Kyushu area such as Kyoto. Use purpose=campaign, prefecture=null and location="" (city/ward unset); ask the user to choose among the seven Kyushu prefectures and wait. Do not search or choose a prefecture before their answer. Preserve other confirmed constraints; this switch is not consent to change them. If the user explicitly specifies a non-Kyushu area in the campaign request, preserve it, explain this tool's Kyushu-only scope and offer a choice between a Kyushu campaign area and ordinary search in their requested area. Do not silently switch either area or mode, or claim that no campaign exists there. A requested nationwide search is explicit nationwide=true, not an unspecified destination. Dates and party are NOT required for discovery or aggregate review analysis. For ふっこう割 use purpose=campaign, inclusive candidate first_check_in/last_check_in and the user's explicit nights/party. It is not an ordinary OTA booking search. For purpose=campaign offer only the returned adult choices 1–5, in the form and text fallback alike. The shared schema accepts up to 8 to preserve unsupported input; that is not the campaign's supported choice range. Preserve the user's city/ward/town/village in location when continuing to search_campaign_availability. The campaign form supports multiple prefectures. For an initial multi-prefecture request, retain the complete formal prefecture names in location and leave the single prefecture unset; never silently pick one. The form confirms each selected prefecture separately. If it cannot open, confirm all named prefectures in text and call search_campaign_availability once per prefecture, preserving other conditions. Campaign-only exception to general no-shortening rules: a multi-night campaign stay is authorized to be adjusted to one night, without another approval question. Pass the original nights/stay dates here, not a silently pre-adjusted request; retain the returned adjusted values and adjustment notice when continuing. Keep the known check-in D; the adjusted checkout is D+1 and nights=1. For that single stay use first_check_in=last_check_in=D, never the original checkout as last. A candidate-date range is separate from stay length: preserve an explicitly supplied first_check_in/last_check_in range; each candidate is one night. Never collapse a conflicting candidate range to a single stay; clarify it. Never invent a missing check-in. Do not change explicit adults; retain original rooms and children in conditions for the campaign reference notices. Ask other missing conditions as usual. Before a search runs, say "1泊に調整しました（未検索）", not "検索しました". Only after a successful campaign search say "1泊に調整して検索しました". Show the retained check-in, next-day checkout and "料金は1泊分です" with this notice; never imply a whole multi-night stay price or multiply one-night prices. A clarification, coverage error or official-period guidance is not a hotel search. If ready after this authorized adjustment, continue with the returned adjusted values; if needs_input, wait for the remaining answers. Do not send nights>1 to the search tool. No hotel, price, availability or booking data is fetched here. ready means only that conditions are complete, never that a hotel is available. Preserve all original hotel/branch/theme/exclusion/budget constraints when continuing with the data tools. Do not represent ordinary OTA results as a campaign. After official-period guidance from search_campaign_availability, follow its explicit normal-price continuation; preserve conditions and label the results ふっこう割対象外・通常料金. Unsupported conditions require explaining limitations; never silently adjust party, area or dates. For status=unsupported, start the answer and any result heading with 未検索（条件非対応） / not searched (unsupported conditions), never "no results", "no availability" or "search results"; no search was performed. A required ryokan classification that cannot be verified means candidate count not assessed, never "Verified matches: 0". For ready, continue to the search tool without another confirmation or UI submission; its optional card is a condition record, not a blocking form or a search result. For needs_input, display the optional form when supported. Do not create a second form or duplicate its questions in chat; wait for the user's answers only in this state. Only if this input form cannot be displayed, ask its questions as a concise numbered list with the supplied choices AND a free-text answer option, all initially unselected. A successful tool call does not prove the form rendered. Do not assert that the form is visible; say it can be used if displayed. If the user reports a loading error or missing form, acknowledge it and use the text fallback immediately; do not insist it is displayed or require repeated retries. Ask only returned missing questions, never a separate children=0 consent for campaign searches. A fixed one-room campaign form has no room-count selector. Do not tell users to enter rooms or children there. Keep a supplied range of candidate check-in dates while asking only for its missing conditions; do not ask the user to choose one date merely to submit an already valid range. Label each candidate stay by its check-in and next-day check-out, not as a multi-night total. Null or blank values are unknown, not permission to choose defaults. Never preselect examples, supported-party limits or the first option as the user's conditions. Keep uncertain/undecided answers unresolved; allow review-only exploration only when the user chooses it. Do not repeat unchanged calls while waiting for an answer. No booking, login, personal information, source fetch or persistent user state.

clarify_hotel_search

Find 九州ふっこう割 (Kyushu fukkowari) plans, candidate dates and official booking URLs. Use this tool first for ふっこう割/復興割/九州ふっこう応援割 requests for eligible hotels, available dates or official direct campaign booking links, not recommend_hotels. If ranking is supplied, preserve its order and briefly explain ranking.label in the user's language, retaining the distinction from an OTA rating or popularity rank. Budget/expensive prompts: min_nightly_price/max_nightly_price filter returned discounted reference prices in JPY; default scope is the whole adult party, one room/night. Explicit per-person budgets use price_scope=per_adult. price_sort=price_desc/price_asc ranks high/low prices before the result limit. Price tiers use HotelME's PRE-discount references within requested place/date/adults: luxury=高級/ラグジュアリー/ハイクラス top10%; upscale=ちょっと贅沢/ご褒美 top20%; premium=ちょっといい/ワンランク上 top30%; standard=普通/中価格帯 middle40%; lower_half=平均より安め/予算を抑える bottom50%; affordable=安い/お手頃/リーズナブル bottom30%; budget=格安/節約重視 bottom10%. These are relative overlapping PRICE tiers, before the discounted budget filter. It is NOT stars, amenities or a quality certification. State this definition. Ties are included; fewer than 10 comparable hotels means unclassified, not no suitable hotels. Do not equate low price with good value/コスパ; that also requires actual review evidence. Unpriced/stale, pre-discount-only and closed-budget offers never count as budget matches. The order covers cached eligible plans, not the world's most expensive hotels. Price ordering is across hotel/date candidates; keep dates with their amounts. With recommended ordering, it ranks ALL matching candidates before limit, prioritizes confirmed campaign plans, and shows distinct hotels before additional dates for the same hotel within each availability group. Explain the supplied evidence threshold and formula when asked. It is not OTA stars, popularity, verified overall quality or cheapest order. Missing/insufficient reviews do not mean low quality. Do not present reference_score as stars or a satisfaction percentage. Counts ending in hotel_dates count hotel/date combinations, not distinct hotels; use ranking's hotel_count fields for hotel counts. Without ranking metadata, the legacy order is check-in date, available plans first, hotel name and hotel ID, then limit. Do not call that recommended or popularity order. Preserve a requested city/ward/town/village in location. It filters verified catalog municipalities before the result limit. Never broaden a requested area to the whole prefecture or infer station walking distance, central-city proximity or attraction access from municipality membership. Unknown areas require clarification, not a prefecture-wide fallback. Keep other hard constraints throughout follow-ups. A named Kyushu station or landmark in location applies a verified straight-line radius before ranking and limit (default 2km; explicit 100m to 20km). If nearby is returned, state its place_name, radius and per-hotel distance as approximate straight distances, preserve nearby.note and its source attribution. These are not walking times or routes. Hotels without coordinates are excluded from proximity matches; no nearby matches does not mean sold out. Keep price filters and other constraints. For a mandatory ryokan / traditional inn request, first call clarify_hotel_search with purpose=campaign and accommodation_type=ryokan, even if dates and party are complete. This search schema has no accommodation-type filter: do not drop that constraint or treat general hotels as verified ryokan. If clarification says unsupported, report not searched / candidate count not assessed, never "Verified matches: 0", "no ryokan" or a searched zero-result count. For multiple selected prefectures, call once for EACH prefecture with the same confirmed dates and party. Never silently use only the first prefecture. Keep each prefecture's results or error/zero-match status identifiable; a failure in one is not proof that it has no eligible plans. Compare only matching price bases. If pets must be accommodated, set pet_friendly=true. The present source has no verified pet policy for the same campaign plan/room/date/party, so the tool returns an evidence limitation, not qualifying offers. A pet review theme, pet-friendly hotel or ordinary pet plan does not prove campaign-plan pet eligibility. Never fill a requested candidate count with unverified or non-campaign alternatives; offer to relax the condition only if the user wants that, not in the matching list. No preliminary ordinary hotel or theme search is needed when prefecture/dates are known. A matching ordinary hotel or OTA vacancy is not evidence of campaign eligibility. If this tool is unavailable, returns zero matches or cannot verify availability, explain that campaign availability is unconfirmed; never substitute Jalan/Rakuten/Ikyu/Booking.com prices or links as campaign offers. Never calculate a campaign discount or payable price from ordinary OTA prices. If the user separately requests ordinary OTA alternatives, clearly label them non-campaign offers; do not silently drop the campaign condition. On a successful response (including zero matches), FIRST follow next_action and prefecture_campaign_status when supplied. budget_exhausted means the requested direct-channel phases cannot currently provide the discount, not fully booked hotels. Explain the budget closure, possible unannounced reopening after cancellations, and the option to search ordinary non-campaign stays before listing any hotels. unknown means reception is unconfirmed, never open. For mixed dates, preserve each date and phase status. Never infer prefecture-wide closure from selected hotel rows. Do not show closed offers as campaign availability. Never recreate withheld links or prices; ordinary alternatives require an explicitly separate non-campaign label. Official wording/URL may be absent; never fabricate a quotation. source_urls are rule references, not necessarily the precise budget announcement. Keep check times internal. After the reception notice, explain official_period when supplied: all_inside means the requested stay nights are within the published official direct-channel calendar. Cite its source_urls, keep verified_date internal, then explain the separate observed inventory. Do not say the period is unverified or that an extension is unconfirmed when this calendar evidence says all_inside. Eligibility applies to stay nights, not checkout: the next day's checkout may be after last_night. This is not a claim of a newly announced extension or remaining subsidy funds; hotel/plan participation, current acceptance and availability remain separate and may end early. Null official_period supplies no calendar conclusion. Exception: status=campaign_period_guidance gives an official calendar decision, not a cache gap or zero availability. Explain the returned prefecture/channel eligible_ranges and excluded_ranges, then follow normal_price_search when supplied: call that ordinary tool with the SAME dates/area/party and all original constraints, and present its actual prices/dated links as ふっこう割対象外・通常料金, not discounted. Enforce result_validation: details/compare cannot filter by prefecture themselves. Never present a returned hotel outside required_result_prefecture as a match; ask about inconsistent hotel/area constraints without substituting another hotel. Do not stop at "outside period" when a supported normal-price continuation is supplied. If partial or no continuation is supplied, follow next_action without changing dates or party. Never infer one nationwide December cutoff: Kagoshima direct continues into February 2027 with an excluded year-end interval. Cite returned official sources. This calendar decision is NOT a hotel search; no prices or availability were fetched yet. Use clarify_hotel_search when prefecture, dates, party or nights are missing. Campaign-only exception: missing children means children=0, without consent or reasking. Keep explicit children (0–6) in tool arguments; children>0 permits an adult-only reference search, not a family offer. Always present adult_only_reference.notice: children are excluded from these prices; family availability and total are unknown. Keep supplied URLs unchanged; set child count/ages on the official booking page. Campaign-only room exception: retain explicit rooms (1–4) in tool arguments. For rooms>1, search one room as a reference without another approval question; do not divide or reduce adults, allocate people across rooms, or multiply prices. Always present single_room_reference.notice after the search: this is one room, not verified multi-room availability or a total for the original room count. The returned request/prices/official URLs cover the searched one-room party only. Reconfigure room count and each room's party on the official site when booking. Never invent or default other conditions. Embedded forms are optional; text works too. On an explicit switch from ordinary search to ふっこう割, if no area is specified for the new campaign request, do not carry forward a prior non-Kyushu area such as Kyoto. First call clarify_hotel_search with purpose=campaign, prefecture=null and location="" (city/ward unset); ask the user to choose among the seven Kyushu prefectures and wait. Do not search or choose a prefecture before their answer. Preserve other confirmed constraints; this switch is not consent to change them. If the user explicitly specifies a non-Kyushu area in the campaign request, preserve it, explain this tool's Kyushu-only scope and offer a choice between a Kyushu campaign area and ordinary search in their requested area. Do not silently switch either area or mode, or claim that no campaign exists there. Campaign-only exception to general no-shortening rules: a multi-night campaign stay is authorized to be adjusted to one night, without another approval question. First pass the original nights/stay dates to clarify_hotel_search with purpose=campaign; retain its returned adjusted values and adjustment notice when continuing. Keep the known check-in D; the adjusted checkout is D+1 and nights=1. For that single stay use first_check_in=last_check_in=D, never the original checkout as last. A candidate-date range is separate from stay length: preserve an explicitly supplied first_check_in/last_check_in range; each candidate is one night. Never collapse a conflicting candidate range to a single stay; clarify it. Never invent a missing check-in. Do not change adults; preserve explicit rooms and children in tool arguments. Ask other missing conditions as usual. Before a search runs, say "1泊に調整しました（未検索）", not "検索しました". Only after a successful campaign search say "1泊に調整して検索しました". Show the retained check-in, next-day checkout and "料金は1泊分です" with this notice; never imply a whole multi-night stay price or multiply one-night prices. A clarification, coverage error or official-period guidance is not a hotel search. Do not send nights>1 to this search tool; its one-night validation remains strict. Both dates are inclusive candidate check-ins, at most 31, not a multi-night stay. For an explicitly requested one-night stay checking in on D and out the next day, use first_check_in=last_check_in=D. D is the user's date, never a suggested default. Preserve the user's area and explicit party; ask unspecified conditions except children. Only this campaign tool supports 1–5 adults, one room and one night. Its cache prices/availability always cover adults only, never children or family totals. When unsupported conditions prevent searching, start the answer and any result heading with 未検索（条件非対応） / not searched (unsupported conditions), never "no results", "no availability" or "search results". For campaign_dates_not_covered, start the answer and any result heading with 未検索（収録期間外）. Do not say 検索結果 / search results, 専用検索で確認しました / we searched, or imply availability was checked: only coverage was checked, not hotel availability. This also applies to explanatory subheadings; use 未検索（収録期間外）：理由と次の確認 for such headings. This is one request-level coverage error, not per-date results. Do not infer which individual dates are inside or outside coverage. If listing the requested dates, label each 未検索（要求全体を実行せず） and explain once that all or some requested dates are not covered; do not label every date outside coverage. Do not change unsupported party conditions. Ordinary vacancies are NOT campaign stock; missing, stale or unverified records are NOT sold out. available_only=False explains non-available statuses, not alternative valid offers. Results cover only monitored cached hotel/date cells, not all hotels. Keep observation/acquisition/check dates and times internal, not in user answers; retain stay dates and campaign deadlines. These observations are not a live availability check. The linked specific plan/room may now be sold out; confirm final availability and conditions on the official booking page. For stale/freshness_unverified/participation_unverified say 現在の対象プランの空室・料金は確認できていません, never imply a check is running or availability. no_campaign_plan_observed is no observed campaign offer, NOT a fully booked hotel. Presence means an offer was seen, not one remaining room; never infer room counts. For campaign_price use the returned kind and price_disclosure. Membership/eligibility, subsidy funds and booking are not guaranteed. Include the supplied official booking_url unchanged for every available match that has one, as a clickable Markdown link. Never replace it with an OTA link, shorten it, strip/add query parameters or construct a missing official URL from a hotel name. No photo URLs are returned. Present campaign offers as text and supplied official booking links; do not add unverified external images or image carousels. Handle separately requested photo research separately, not as campaign evidence. If booking_url is missing, say no verified official booking destination was supplied. dated_search means verified date/party prefill; selection_required means an observed booking page: say 予約ページで宿泊日・人数・対象プランを確認・選択してください. A plan-level URL may open a month calendar; never claim its date is already selected. Link prices and membership conditions can differ from hotel-level aggregates. Never invent missing URLs, substitute marketing home pages or promise booking success. This is read-only, never books, browses or refreshes a source. No login is needed. When supplied, participation_basis=official_site_plan means the monitor observed a strongly matching official campaign plan, not prefectural-list certification. other_campaigns identifies other campaigns, not 九州ふっこう割 stock. freshness_notice=source_monitor_delayed is a feed-wide caution, not a replacement for individual statuses; retain no_campaign_plan_observed when returned. Say 最新の空室・料金は予約先で確認してください, not monitoring jargon or an exact timestamp. Never mention missing optional fields as established facts. For user answers in every language, including English and follow-ups: keep internal identifiers such as discount_rule_id out of the answer. Keep observation/check/acquisition timestamps internal; show stay dates and campaign deadlines, not exact observation times. Retain that this is not a live quote. Use traveler-facing language, not internal monitoring terminology: say 参考料金, not 観測価格/観測料金. Only for options with returned usable prices say HotelMEで料金を確認できたホテル; otherwise say 検索対象ホテル, not 監視対象施設. For stale or freshness-unverified data say 現在の空室・料金は確認できていません。最新の空室・料金は予約先で確認してください, not 情報が古く確認中. For no_campaign_plan_observed say この日はキャンペーン対象プランの販売が見当たりません。満室や割引受付の終了を意味するものではありません. This is a recent search result, not a guarantee that no plan is sold now; do not relabel it 確認中 or bookable. price_unavailable_reason=price_stale means only the price is unconfirmed; retain the returned inventory status and never invent a price or claim rooms are sold out. Do not imply a refresh is running or complete, guaranteed stock, or a live payable quote. Initially show 3–5 matching hotel/date options, or fewer if fewer are returned; respect a requested count and never invent options or imply exhaustive coverage. Never fill that count with ordinary hotels or plans that fail or have not been verified against the user's mandatory campaign, area or pet conditions. A review theme is not proof that the same campaign plan/room accepts pets. For EACH displayed option, include its supplied official booking_url unchanged, or say 確認できた公式予約リンクはありません / No verified official booking link was returned. Never substitute an OTA link, invent a missing-link reason or reuse another option's URL. For EACH selection_required option, place beside its link: 予約先で宿泊日・人数・対象プランを選択 / Select dates, guests and the campaign plan on the booking site. For check_on_site, say availability is unconfirmed; never label it bookable. Keep each option's price type, party and restrictions clear. Combine identical conditions only after labelling every price as 大人N名合計・1室1泊 (total for N adults, one room, one night), never an ambiguous /N名 or per-person amount. Never divide amounts or relabel a pre-discount per-person website amount as the returned discounted total. The pre-discount and discounted columns must both describe the same requested party. For a discrepancy, compare the same dates, guests, room, plan, meals, taxes, membership and discount stage; never explain a pre-discount discrepancy using the computed-price 99-yen rounding note or silently replace a supplied amount. Combine identical conditions into one concise shared note only when they truly apply to every displayed option; retain any differing payment, coupon or refund conditions beside the relevant option. For cheapest/price order, compare only returned amounts with the same party and price kind/basis. Put unknown-price options in a separate unpriced section after priced options. Never rank pre-discount and discounted amounts together or claim market-wide cheapest. Campaign forms ask only missing dates, area or adults; searched rooms=1 is fixed. Preserve original rooms for the reference notice; never divide or reduce adults. Do not ask users to find room-count or children controls that the form does not have. Do not imply that a clarification form has already searched availability. When single_room_reference is present, room_allocation=unknown means each room's guest allocation is unverified. The returned request.adults are ALL requested adults in ONE reference room, not a per-room allocation for the original room count. In final answers, follow-ups, translations and booking-site instructions, never infer or propose an equal split or each room's guest count from adults and requested_rooms. A user-supplied allocation may be repeated only as requested, never as verified hotel availability or pricing. An earlier assistant suggestion is not user confirmation. Never divide adults or divide/multiply a returned price to produce per-person or multiple-room totals. Keep every supplied booking URL unchanged. Continue the one-room reference search without asking for a room allocation; say 指定の大人全員で1室を利用する条件の参考情報です。各室の人数配分は未確認です。予約先でご希望の人数配分を設定してください. Use only returned campaign_price amounts, never calculate a discount or payable price. Map kind=discounted_shown to 割引後 and kind=pre_discount_only to 割引前. Do not print the machine kind names. For each amount show [公式サイト; 割引後 / 割引前; 消費税込; 宿泊税・入湯税は別; 1室・1泊・大人N名; 参考料金・確定料金ではありません]. pre_discount_only.amount=null is not a discounted price. pre_discount_amount is 対象プランの割引前料金, not the hotel's 通常最安値. Never calculate or emphasize the difference as savings/お得額. Explain price_unavailable_reason without inventing a price. Include price_disclosure. For price_unavailable_reason=members_only say 会員限定など条件付きプランのみ. If members_only=true, preserve that restriction; never claim nonmembers are eligible. discount_conditions rate/cap are rules, not a promise of eligibility or remaining funds. Cap is 1人・1旅行, not per night. State supplied payment and coupon_code without inventing missing conditions. If discount_conditions.payment is absent say 支払方法は公式ページで確認してください. budget_status=open/scheduled/exhausted is an observed budget state, not guaranteed funds; keep budget_checked_at internal, not in user answers. Missing budget_status means 県の予算の状態は未確認. campaign_budget_exhausted means 取得した情報では対象の割引予算の受付は終了しています。割引対象の空室とは案内しないでください. Hotel rooms may still be sold without this discount. Never treat a closed budget as hotel-wide fullness or general sales closure. A single option does not establish prefecture-wide or all-phase closure; use that scope only when explicitly established by the returned authoritative budget summary. A returned exhausted budget does not support a discounted quote even if the booking page still lists the plan. scheduled/budget_not_started means 取得した情報では受付開始予定です。現在の受付状況は公式ページで確認してください. Do not turn an observed scheduled state into a claim that registration has not started now. A new campaign phase, current acceptance and remaining funds need fresh official evidence; do not infer them from an old budget state, a plan listing or a rule identifier. Treat each price and its conditions as one inseparable bundle. In a short answer, table, mobile summary, translation (including English), follow-up or reordered list, retain the price kind/estimate, whole-party one-room one-night unit, redemption steps, payment, membership and booking-site selection requirements beside that option. A generic availability/budget disclaimer cannot replace required coupon or refund steps. If space is limited show fewer options, never remove the conditions. Keep bundles with their original matches when reordering; never apply one option's conditions to another. Match indices and the words price bundle are model-only, never user-facing labels. Translate the following labels into the user's language without dropping their meaning. Only quote API kind=discounted_computed as 割引後（計算値・目安。公式サイトの割引前の表示額に県の割引規則（率・上限）を当てた値。宿の端数処理で最大99円高いことがある）, never as 公式サイトの表示額 or 予約時の金額. Include returned pre_discount_amount labelled 割引前の表示額, rate/cap and the same tax/party/not-live labels. Always explain applied_at: on_site=宿で割引; coupon_code=クーポンコードを入力; staynavi=STAYNAVIでクーポンを取得; rebill=支払いは割引前の額で、割引は後日返金。目安は返金後の負担額. For staynavi/coupon_code add クーポンを取得・入力しないと割引前の額になる. If applied_at is absent say 割引の受け方は公式ページで確認してください. Quote payment and budget conditions too; missing budget_status means 県の予算の状態は未確認. Never compute from pre_discount_amount or rate/cap yourself, including pre_discount_only. For budget_not_started never quote a discounted amount. Keep labels when summarizing/translating. If matches are empty or status_counts includes stale/freshness_unverified, available_only=false may return check_on_site destinations; preserve every other condition. check_on_site does NOT establish available rooms or a price. Say 現在の空室・料金は確認できていません without displaying availability_last_checked_at. 公式ページで空室と料金を確認してください. Do not describe it as available/bookable. Include the returned URL unchanged. achieved_interval_sec is an observed monitoring interval, not a future refresh guarantee.

search_campaign_availability