Skip to main content
Glama

HawaStay – Waikiki hotel finder

ワイキキのホテルを比べる / Compare Waikiki hotels

compare_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.

2〜5軒を泊数つきで比べ、リゾートフィーの合計(1泊の額×泊数)と設備を並べる。宿泊料金そのものは返さない。slug が分からなければ先に search_hotels を条件なしで呼ぶ。 / Compare 2–5 hotels: resort fee total (per night × nights) and amenities. Room rates are not returned.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slugs": "<slugs>",
      "nights": "<nights>"
    },
    "name": "compare_hotels"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugsYesホテルの slug(例 halekulani)/ hotel slugs
nightsYes泊数 / number of nights

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, but the description adds real behavioral context: room rates, parking fees and deposits are absent from the dataset and must never be guessed, resort fees are computed as per-night × nights, and each hotel's detail_url must be cited as the source. It stops short of describing output shape or ordering of the comparison.

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?

The content is front-loaded and every clause carries information (purpose, data limits, citation rule, procedure, fallback). The bilingual duplication doubles the length, though each language version is tight and the dual-language presentation appears deliberate for its Japanese-traveler audience.

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

Completeness4/5

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

For a two-parameter read-only tool with no output schema, the description covers what is compared (resort fee total, amenities), what is deliberately not returned (room rates, parking, deposits), and the citation requirement. Only minor gaps remain, such as how results are ordered or presented.

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 schema already documents both fields, but the description adds meaning: the comparison must cover 2–5 hotels, slugs originate from search_hotels, and nights is used to extrapolate the resort fee total rather than just being a count. That is genuine added semantics beyond the JSON schema descriptions.

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

Purpose5/5

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

States a specific verb+resource+scope: find/compare Waikiki hotels by washlet/bathtub/kitchen amenities and resort-fee-inclusive totals. It also names its data source (HawaStay) and explicitly separates itself from single-hotel lookup and search by telling the agent to call search_hotels first when slugs are unknown.

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 clear when-to-use framing (comparing 2–5 hotels by amenities and resort fees) and a concrete fallback: if slugs are unknown, call search_hotels without filters first. It does not spell out when to prefer get_hotel instead of comparing, leaving one boundary implicit.

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