Skip to main content
Glama

Hotel Detail by Name (one specific hotel)

get_ota_hotel_detail

Full detail (rooms, live prices, facilities, photos, reviews) from Booking.com for one named hotel over a date range, for requests about a single hotel rather than a whole city (search_hotels_live lists a city). The name is resolved through the city's listings, so it takes the hotel name together with its city; a Booking.com URL from an earlier result skips that lookup. TravelOpen direct listings are covered by get_hotel_detail. The fetch is live and takes up to about two minutes; under heavy load it can return not-found.

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": {
      "checkIn": "<checkIn>",
      "checkOut": "<checkOut>"
    },
    "name": "get_ota_hotel_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity of the hotel, used to resolve the name, e.g. 'Da Nang'. Required with hotelName.
roomsNoNumber of rooms (default 1)
adultsNoNumber of adults (default 2)
checkInYesCheck-in date YYYY-MM-DD. Must be today or later.
checkOutYesCheck-out date YYYY-MM-DD. Must be after checkIn.
languageNoOptional UI language. Indonesian (id) cannot be detected from text, so for Indonesian this is how the language is set.
childAgesNoAge of each child. Child-aware room detail is limited to Booking.com and Agoda app adapters.
hotelNameNoName of the hotel, e.g. 'Mercure Danang French Village Bana Hills'. Required unless propertyUrl is given.
queryTextNoShort excerpt (one sentence at most) of the guest's latest message in their own words, used only to detect the reply language; it is not stored or forwarded. It carries no names, contact details or other parts of the conversation.
propertyUrlNoBooking.com property URL from an earlier result (hotel.prices.booking.url); skips the name lookup.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / childAges
      Added value: +{
      +  "description": "Age of each child. Child-aware room detail is limited to Booking.com and Agoda app adapters.",
      +  "items": {
      +    "maximum": 17,
      +    "minimum": 0,
      +    "type": "integer"
      +  },
      +  "maxItems": 20,
      +  "type": "array"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Adds context annotations do not carry: the fetch is live, can take 'up to about two minutes', and 'under heavy load it can return not-found' — a real failure mode the agent must plan around. It also explains the internal name-resolution dependency on city listings, which predicts failure when city is wrong. Minor gap: it does not say whether prices are cached/quoted or how repeated calls behave. Note that readOnlyHint=false is an odd annotation for a described read fetch, but the description itself makes no write claim, so this is a mismatch rather than a description contradiction.

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?

Front-loaded with what the result contains, then scope, then mechanics, then the latency caveat — a sensible order with no filler. It is dense, with long clause-chained sentences, but every sentence carries distinct information rather than restating the title.

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 10-parameter, no-output-schema tool, the description covers purpose, the two lookup paths, sibling alternatives, latency and a documented failure mode — enough to call it correctly. It stops short of describing the structure or variability of the returned detail (e.g., whether reviews/photos are always present, or how many results), which an agent forming expectations would benefit from given there is no output 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%, so the baseline is 3, and the description earns a bump by explaining the relationship between parameters that the schema only states individually: hotelName must be paired with city for resolution, and propertyUrl bypasses that lookup entirely. It does not cover rooms/adults/childAges/language semantics in prose, but the schema documents those fully, so no value is lost.

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 and resource with its payload enumerated: 'Full detail (rooms, live prices, facilities, photos, reviews) from Booking.com for one named hotel over a date range'. It also explicitly separates scope from the sibling search tool ('for requests about a single hotel rather than a whole city (search_hotels_live lists a city)') and names get_hotel_detail as the path for TravelOpen direct listings.

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

Usage Guidelines5/5

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

Explicit routing conditions: use this for a single named hotel, use search_hotels_live for a city, use get_hotel_detail for TravelOpen direct listings. It also gives two valid invocation paths (name + city, or a Booking.com propertyUrl that 'skips that lookup'), which is exactly the guidance an agent needs before choosing parameters.

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