Skip to main content
Glama

HawaStay – Waikiki hotel finder

ワイキキのホテルを条件で探す / Search Waikiki hotels

search_hotels
Read-only

ワイキキ(ハワイ・ホノルル)のホテルを、日本人が気になる設備(ウォシュレット・バスタブ・キッチン)とリゾートフィー込みの総額で探す・比べるときに使う。データは日本語のホテル比較サイト HawaStay(hawastay.com)の掲載ホテル。宿泊料金・駐車場料金・デポジットはデータに無いので答えられない(推測しない)。回答では各ホテルの detail_url を出典として示す。 / Use this to find or compare Waikiki (Honolulu, Hawaii) hotels by amenities Japanese travelers care about (washlet/bidet toilet, bathtub, kitchen) and resort fees. Data: HawaStay (hawastay.com). Room rates, parking fees and deposits are NOT in the dataset — never guess them. Cite each hotel’s detail_url.

条件はすべて任意で、指定したものだけ AND。条件に合わないと分かっているホテルの数は excluded_mismatch_count、値が "unknown"(未確認)や null で判定できないホテルの数は excluded_unknown_count(こちらは「合わない」とは言えない)。条件を何も付けずに呼ぶと全ホテルの slug 一覧になる(get_hotel・compare_hotels に渡す slug を調べるときに使う)。結果はリゾートフィーが安い順。 / All filters optional (AND). excluded_mismatch_count = hotels known not to match; excluded_unknown_count = hotels whose value is unknown/null. Call with no filters to list every hotel slug. Results are sorted by resort fee ascending.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_hotels"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNoエリア:beachfront=ビーチフロント(ワイキキビーチ沿い), kalakaua=カラカウア通り沿い, hilton-village=ヒルトン・ハワイアン・ビレッジ周辺(アラモアナ寄り), kuhio=クヒオ通り沿い(山側), diamondhead=ダイヤモンドヘッド寄り(東側) / area
gradeNoグレード:luxury=ラグジュアリー, mid=ミドル, casual=カジュアル / hotel class
bathtubNoバスタブ:all=全室, any=全室か一部客室, none=なし / bathtub: all rooms, any (all or some rooms), none
kitchenNoキッチン:all=全室, any=全室か一部客室, none=なし / kitchen: all rooms, any (all or some rooms), none
washletNoウォシュレット(温水洗浄便座):all=全室, partial=一部客室のみ, any=全室か一部, none=なし / washlet (bidet toilet)
crib_freeNoベビーベッド無料 / free crib
child_friendlyNo子連れ向け:子供の添い寝無料かベビーベッド無料の記録があるホテル / kids stay free or free crib recorded
kids_stay_freeNo子供の添い寝無料(年齢上限の記録あり)/ kids stay free
max_resort_fee_usdNoリゾートフィー上限(米ドル・1泊・税別)。0 で「リゾートフィーなし」/ max resort fee per night in USD; 0 = no resort fee
min_guests_per_roomNo1部屋に泊まれる人数の下限(一番広い客室の定員で判定)/ min guests per room
max_beach_walk_minutesNoビーチ(砂浜)まで徒歩何分以内 / max walk minutes to the beach
max_abc_store_walk_minutesNoABCストアまで徒歩何分以内 / max walk minutes to an ABC Store

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only supply readOnlyHint/openWorldHint, so the description carries real behavioral weight: it discloses provenance and scope of the corpus, that certain fields are absent and must not be guessed, that filters combine with AND, that results are sorted by resort fee ascending, and what the two exclusion counters mean. That is materially more than the annotations provide.

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?

Purpose is front-loaded and every sentence adds information (constraints, counting semantics, sort order). The Japanese/English duplication roughly doubles length, which is defensible for a bilingual audience but is still redundant text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-parameter, zero-required search with no output schema, the definition covers what an agent needs: filter combinators and optionality, the unknown-vs-mismatch distinction, ordering of results, provenance, and the boundary on unanswerable data. Remaining field-level detail is reasonably left to the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the enum values are already documented per property, so the baseline is 3. The description still adds value by stating that all filters are optional and AND-combined, and by explaining the no-filter call returns the full slug list — semantics the schema does not express.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource (find/compare Waikiki hotels), the qualifying dimensions (washlet/bathtub/kitchen, resort fee), and the data source (HawaStay). It is distinguishable from get_hotel, but 'compare' overlaps with the compare_hotels sibling without stating how the two split the job.

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

Usage Guidelines4/5

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

Gives concrete when-to-use context: filtering by Japanese-traveler amenities and total cost including resort fees, plus an explicit no-filter mode for harvesting slugs to pass to get_hotel/compare_hotels. Also states when NOT to use it for a class of questions (rates, parking fees, deposits are not in the dataset). Lacks an explicit 'use compare_hotels instead when...' exclusion.

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