Skip to main content
Glama

Get one hotel's full-stay rooms and prices

get_accommodation_offers
Read-onlyIdempotent

Returns one named or identified hotel's full-stay property data and live room offers for specified dates and occupancy. When the user refers to a hotel from a previous search_accommodations result by list position or partial name, copy its propertyId exactly if the match is unique; never shorten, combine, or use a placeholder ID. Ask for clarification if several hotels match. Use hotelName and optional destination when no exact propertyId is available. Includes wholesale room types and photos, breakfast, refundability, cancellation terms, public-rate comparisons, wholesale prices or price bands, and Brek links. Public-only room types are excluded. Wholesale options priced above their public comparison are marked sold_out without a price; the public comparison remains available. Single-room and multi-room stays are supported through aggregate occupancy plus optional per-room arrangements. Prices are rechecked on Brek.

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": "get_accommodation_offers"
  }
}

Input Schema

NameRequiredDescriptionDefault
roomsNoWhole-number room count from 1 to 3. Each room requires at least one adult.
adultsNoWhole-number total adult count from 1 to 16 across all rooms.
currencyNoOnly specify a currency when the traveler explicitly requests one. Otherwise omit it so Brek can use the visitor country, then locale, then USD. Supported: EUR, USD, INR, GBP, AUD, CAD, ARS, TRY, COP, CLP, SEK, MXN, IDR, BRL.
timeZoneNoOptional IANA time-zone fallback for resolving relative stay dates; destination or property location takes precedence.
hotelNameNoExact hotel name when propertyId is unavailable.
dateIntentNoUse only when the user explicitly requests tonight. Resolves check-in as the current local date and check-out as the following date; otherwise provide both stay dates.
propertyIdNoExact Brek property ID copied from a previous search result or Brek stay URL. Do not guess, truncate, combine, or pass a placeholder; use hotelName if unsure.
checkinDateNoRequired with checkoutDate unless the user explicitly requested tonight. Use YYYY-MM-DD.
destinationNoOptional city or region for disambiguating hotelName.
checkoutDateNoRequired with checkinDate unless the user explicitly requested tonight. Use YYYY-MM-DD.
childrenAgesNoWhole-number ages from 0 to 17 for up to 8 children at check-in.
roomArrangementsNoExact per-room occupancy. Example: room 1 has 2 adults and room 2 has 2 adults plus children ages 4 and 2 => [{adults:2,childrenAges:[],infants:0},{adults:2,childrenAges:[4,2],infants:0}]. Array length equals rooms, and aggregate guests equal adults and childrenAges.
availabilityTokenNo

Output Schema

NameRequiredDescriptionDefault
stayYes
offersYes
statusNo
messageNo
propertyYes
propertyIdYes
requiredInputNo
priceDisclosureYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed39 schema fields changed
    • changedInput schema / properties / adults / description
      Previous value: -"Total adult guests."New value: +"Whole-number total adult count from 1 to 16 across all rooms."
    • removedInput schema / properties / adults / maximum
      Removed value: -16
    • removedInput schema / properties / adults / minimum
      Removed value: -1
    • changedInput schema / properties / adults / type
      Previous value: -"integer"New value: +"number"
    • changedInput schema / properties / childrenAges / description
      Previous value: -"Age of each child at check-in."New value: +"Whole-number ages from 0 to 17 for up to 8 children at check-in."
    • removedInput schema / properties / childrenAges / items / maximum
      Removed value: -17
    • removedInput schema / properties / childrenAges / items / minimum
      Removed value: -0
    • changedInput schema / properties / childrenAges / items / type
      Previous value: -"integer"New value: +"number"
    • removedInput schema / properties / childrenAges / maxItems
      Removed value: -8
    • changedInput schema / properties / roomArrangements / items / properties / adults / description
      Previous value: -"Adults staying in this specific room."New value: +"Whole-number adult count from 1 to 8 in this specific room."
    • removedInput schema / properties / roomArrangements / items / properties / adults / maximum
      Removed value: -8
    • removedInput schema / properties / roomArrangements / items / properties / adults / minimum
      Removed value: -1
    • changedInput schema / properties / roomArrangements / items / properties / adults / type
      Previous value: -"integer"New value: +"number"
    • addedInput schema / properties / roomArrangements / items / properties / childrenAges / $ref
      Added value: +"#/properties/childrenAges"
    • changedInput schema / properties / roomArrangements / items / properties / childrenAges / description
      Previous value: -"Ages of children staying in this specific room."New value: +"Whole-number ages from 0 to 17 for up to 8 children staying in this room."
    • removedInput schema / properties / roomArrangements / items / properties / childrenAges / items
      Removed value: -{
      -  "maximum": 17,
      -  "minimum": 0,
      -  "type": "integer"
      -}
    • removedInput schema / properties / roomArrangements / items / properties / childrenAges / maxItems
      Removed value: -8
    • removedInput schema / properties / roomArrangements / items / properties / childrenAges / type
      Removed value: -"array"
    • changedInput schema / properties / roomArrangements / items / properties / infants / description
      Previous value: -"Number of infants staying in this room."New value: +"Whole-number infant count from 0 to 4 in this room."
    • removedInput schema / properties / roomArrangements / items / properties / infants / maximum
      Removed value: -4
    • removedInput schema / properties / roomArrangements / items / properties / infants / minimum
      Removed value: -0
    • changedInput schema / properties / roomArrangements / items / properties / infants / type
      Previous value: -"integer"New value: +"number"
    • removedInput schema / properties / roomArrangements / maxItems
      Removed value: -3
    • removedInput schema / properties / roomArrangements / minItems
      Removed value: -1
    • changedInput schema / properties / rooms / description
      Previous value: -"Number of rooms. Each room requires at least one adult."New value: +"Whole-number room count from 1 to 3. Each room requires at least one adult."
    • removedInput schema / properties / rooms / maximum
      Removed value: -3
    • removedInput schema / properties / rooms / minimum
      Removed value: -1
    • changedInput schema / properties / rooms / type
      Previous value: -"integer"New value: +"number"
    • addedOutput schema / properties / message
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / requiredInput
      Added value: +{
      +  "items": {
      +    "enum": [
      +      "adults",
      +      "children",
      +      "childrenAges",
      +      "rooms",
      +      "roomArrangements"
      +    ],
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • removedOutput schema / properties / status / const
      Removed value: -"hotel_not_found"
    • addedOutput schema / properties / status / enum
      Added value: +[
      +  "hotel_not_found",
      +  "occupancy_invalid"
      +]
    • changedOutput schema / properties / stay / properties / adults / type
      Previous value: -"integer"New value: +"number"
    • changedOutput schema / properties / stay / properties / children / type
      Previous value: -"integer"New value: +"number"
    • changedOutput schema / properties / stay / properties / childrenAges / items / type
      Previous value: -"integer"New value: +"number"
    • changedOutput schema / properties / stay / properties / roomArrangements / items / properties / adults / type
      Previous value: -"integer"New value: +"number"
    • changedOutput schema / properties / stay / properties / roomArrangements / items / properties / childrenAges / items / type
      Previous value: -"integer"New value: +"number"
    • changedOutput schema / properties / stay / properties / roomArrangements / items / properties / infants / type
      Previous value: -"integer"New value: +"number"
    • changedOutput schema / properties / stay / properties / rooms / type
      Previous value: -"integer"New value: +"number"
  2. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the bar is lower. The description still adds real value by disclosing that public-only room types are excluded, that wholesale options priced above their public comparison are flagged sold_out with no price while the comparison stays visible, and that prices are rechecked on Brek. It does not cover failure modes, latency, or what happens when no offers exist.

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 the core purpose, then identity-resolution rules, then offer behavior — a sensible order. It is dense but nearly every clause carries information; the long enumeration of included fields (photos, breakfast, refundability, cancellation terms, price bands, Brek links) is the one stretch that could be tightened.

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

Completeness5/5

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

For a 13-parameter, open-world lookup with an output schema, the definition covers identity resolution, occupancy modes, date handling, and the sold_out exclusion rule that an agent would otherwise misreport. Nothing needed to invoke it correctly appears to be missing.

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 92%, so the schema already carries nearly all parameter meaning, including the propertyId copying rule and the currency fallback chain that the description partly repeats. The description does clarify how aggregate occupancy relates to optional per-room arrangements, but it says nothing about availabilityToken, which is undocumented in both places. Baseline 3 applies.

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 opening sentence names a specific verb and resource — returns one identified hotel's full-stay property data and live room offers for given dates and occupancy — which is exactly the single-hotel counterpart to search_accommodations. An agent can tell it apart from both siblings without opening a schema.

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?

It gives explicit routing rules: use propertyId copied from a prior search_accommodations result when the match is unique, fall back to hotelName plus optional destination when no exact ID exists, and ask for clarification when several hotels match. When-not conditions (never shorten, combine, or use a placeholder ID) are stated outright.

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