Skip to main content
Glama
mrslbt

rakuten-mcp

by mrslbt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Search Rakuten Travel Hotels (by Area)

travel_simple_hotel_search
Read-onlyIdempotent

Search Rakuten Travel hotels by area code hierarchy or latitude/longitude coordinates. Returns hotel summaries with prices, addresses, review stats, and ratings.

Instructions

Search Rakuten Travel hotels by area code (japan → prefecture → city → district) or by latitude/longitude coordinates. Returns hotel summaries with prices, addresses, review stats, and ratings. Use travel_get_area_class to discover area codes.

[JA] 楽天トラベルのホテルをエリアコード階層(日本→都道府県→市区町村→詳細)、または緯度経度で検索します。価格、住所、レビュー、評価を含むホテル一覧を返します。エリアコードは travel_get_area_class で取得できます。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hitsNoResults per page (1–30). 取得件数。
pageNoPage number. ページ番号。
latitudeNoLatitude (decimal degrees) for coordinate search. 緯度。
longitudeNoLongitude (decimal degrees) for coordinate search. 経度。
searchRadiusNoSearch radius in kilometers (0.1–3.0) when using lat/lon. 検索半径(km、0.1〜3.0)。
largeClassCodeNoLarge area class (e.g., 'japan'). Use travel_get_area_class to discover. 大エリア(例: 'japan')。
smallClassCodeNoCity-level code (e.g., 'tokyo'). 市区町村。
detailClassCodeNoDistrict-level code (e.g., 'A'). Required by Rakuten whenever the chosen smallClassCode has `details` in travel_get_area_class (e.g. Kyoto city has A–E); optional otherwise. 詳細エリア。travel_get_area_class で details を持つ市区町村(例: 京都市 A〜E)では必須。
middleClassCodeNoPrefecture-level code (e.g., 'tokyo'). 都道府県。

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.0
    • changedInput schema / properties / detailClassCode / description
      Previous value: -"District-level code (e.g., 'A'). 詳細エリア。"New value: +"District-level code (e.g., 'A'). Required by Rakuten whenever the chosen smallClassCode has `details` in travel_get_area_class (e.g. Kyoto city has A–E); optional otherwise. 詳細エリア。travel_get_area_class で details を持つ市区町村(例: 京都市 A〜E)では必須。"
  2. Addedv1.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish safe read-only, idempotent, open-world behavior. The description adds meaningful return context—hotel summaries with prices, addresses, review stats, and ratings—which matters because there is no output schema; it still omits auth, rate, and full pagination behavior.

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 English portion is front-loaded and efficient: purpose, return contents, then prerequisite. The Japanese translation duplicates the same content, which adds length but may be intentional localization; otherwise there is little waste.

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?

Given the rich parameter schema and safety annotations, the description covers the key missing pieces: purpose, return contents, and the area-code discovery prerequisite. It is sufficient for calling the tool correctly, though explicit alternative-routing guidance and pagination/output details are absent.

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 description coverage is 100%, so all nine parameters are already documented in the schema. The description reinforces the area-code hierarchy and points to travel_get_area_class, but adds no syntax or format details beyond what the schema provides.

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?

States a specific verb and resource: search Rakuten Travel hotels by area-code hierarchy or latitude/longitude. It is clear what the tool does, but it does not explicitly distinguish itself from sibling search tools such as travel_keyword_hotel_search or travel_vacant_hotel_search.

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

Usage Guidelines3/5

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

It gives one useful prerequisite: use travel_get_area_class to discover area codes. However, it does not explain when to choose this tool over keyword, vacancy, ranking, or detail-search siblings, nor does it state exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools