Skip to main content
Glama

HawaStay – Waikiki hotel finder

ワイキキのホテル1軒の全データ / Get one Waikiki hotel

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

1軒の全項目(リゾートフィー・ウォシュレット・バスタブ・キッチン・ビーチとABCストアまでの徒歩分数・子連れ情報・詳細ページURL・確認日)を返す。 / Returns every field for one hotel.

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": {
      "slug": "<slug>"
    },
    "name": "get_hotel"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesホテルの slug(例 sheraton-waikiki)/ hotel slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover readOnly and closed-world, so the description's added value is the dataset scope (HawaStay, Waikiki only) and the explicit list of data NOT available, which prevents hallucinated pricing. Without an output schema, the enumeration of returned fields also carries real informational weight; a note on what happens for an unknown slug is the only meaningful omission.

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 dual-language duplication doubles the length, but the structure is sound: use case and constraints first, return contents second. Every sentence contributes a distinct fact (scope, exclusions, citation rule, field list) with no filler.

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 single-record read with one parameter and no output schema, the definition covers scope, exclusions, returned fields, and citation expectations. Only the unknown-slug behavior and how to discover a slug are left unaddressed.

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

Parameters3/5

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

Schema coverage is 100% and the single slug parameter is already documented with an example (sheraton-waikiki). The description adds no further meaning about slug format, source, or lookup, so baseline 3 applies.

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?

The second paragraph states a specific verb and resource: it returns every field for one hotel, including resort fee, washlet, bathtub, kitchen, walk times, kid info, detail_url and verification date. The '1軒' / 'one hotel' framing plus the required slug distinguishes it implicitly from the list-oriented siblings search_hotels and compare_hotels, though no sibling is named.

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?

It gives clear context for use (Waikiki hotels, amenities Japanese travelers care about, resort-fee-inclusive totals), explicit exclusions (room rates, parking fees and deposits are NOT in the dataset — never guess), and an output rule (cite detail_url). What it lacks is the routing instruction for how to obtain a slug, which is the only reason an agent would need a sibling first.

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