Skip to main content
Glama

子連れ条件×エリアで宿を検索

search_hotels
Read-onlyIdempotent

赤ちゃん・子連れ向け設備の検証済み条件(53種・list_conditions参照)とエリア・子どもの年齢・価格で日本の宿を検索します。宿名が分かっている場合は keyword で直接検索できます。結果の page URL が施設の詳細・予約ページです(地図は施設ページにあります)。

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エリア名。例: "箱根" "沖縄本島"
sortNo並び順。既定=rating(楽天評価順)
limitNo取得件数(既定10・最大20)
keywordNo宿名で検索(部分一致・日本語名/英語名/slug対応)。例: "グリーンプラザ軽井沢"
child_ageNo子どもの年齢(歳)。対象年齢に合う宿へ絞り込み
max_priceNo1名1泊あたり上限額(円・目安)
conditionsNo条件ID(AND検索)。例: ["baby_bed_rental","bath_pre_potty_ok"]
prefectureNo都道府県名またはJISコード。例: "神奈川県" / "14"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent and closed-world behavior, so the description only needs to add what they cannot say. It does: results carry a page URL that is the facility's detail/booking page, and the map lives on that facility page rather than in the search result — genuinely useful disclosure given there is no output schema. It does not mention result payload fields beyond the URL or any throttling behavior, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the primary capability, then the keyword fallback, then the return-value note. Nothing is repeated from the schema and no sentence is 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?

With eight parameters and no output schema, the description does the essential jobs: it points to list_conditions for the condition vocabulary and describes what the returned URL represents. What is missing is a note on how area/prefecture strings are resolved (e.g. via list_areas) and any indication of the returned record's other fields, both of which matter for a discovery tool with no declared output shape.

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%, so the schema already carries per-parameter descriptions and the baseline would be 3. The description still adds real meaning on top: it explains that conditions must be resolved against list_conditions (53 verified types) and that the filters combine area, child age and price — framing that the flat schema does not convey. It adds no syntax detail for values like prefecture codes, but the schema covers those.

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?

The description names a specific verb and resource ('日本の宿を検索します') and enumerates the actual filter dimensions (verified family-friendly conditions, area, child age, price). It also separates the two modes of use — condition-based search versus direct keyword lookup by hotel name — which is the distinction an agent needs before choosing a call.

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 explicit routing guidance in one direction: use keyword when the hotel name is already known, and consult list_conditions for the 53 condition IDs. It stops short of the reverse guidance — e.g. when to prefer get_hotel for a full record, or list_areas to resolve an area name before searching — so the when-not side is left 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