Skip to main content
Glama

Search multiple Brek hotels

search_accommodations
Read-onlyIdempotent

Searches and compares multiple hotels in a city, neighborhood, airport, landmark, or other destination. Every search requires both checkinDate and checkoutDate, or dateIntent=tonight when the user explicitly asks for tonight. If the user supplied neither, ask for stay dates before calling; do not choose dates for them. Supports occupancy, price range, star rating, guest score, property types, amenities, cancellation preference, and sort order. Returns an ordered list with property IDs, hotel facts, wholesale prices or price bands, public-rate comparisons, and Brek links. For a follow-up by position or partial hotel name, match against the most recent relevant search list. If one hotel matches, copy its propertyId exactly into get_accommodation_details or get_accommodation_offers; never shorten, combine, or replace IDs with placeholders. If the ID is unavailable, pass hotelName and optional destination instead. If several hotels match, ask which hotel the user means. Intended for destination discovery and multi-hotel comparison; room-level offers for one property are not included.

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": {
      "destination": "<destination>"
    },
    "name": "search_accommodations"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
sortNoUse top-picks for recommended, distance for nearest, total for price ascending, total-desc for price descending, and reviews for guest review score (not hotel stars). Aliases: price_low_to_high / total price ascending -> total; price_high_to_low / total price descending -> total-desc; rating / guest reviews -> reviews. Unknown sorting returns normal correction guidance.top-picks
roomsNoWhole-number room count from 1 to 3. Each room receives the default of 2 adults when adults is omitted.
adultsNoWhole-number total adult count from 1 to 10 across all rooms. When omitted, Brek defaults to 2 adults per room.
childrenNoWhole-number total child count from 0 to 8; when omitted, uses childrenAges.length.
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.
latitudeNoOptional latitude when already known.
timeZoneNoOptional IANA time-zone fallback for resolving relative stay dates; destination or property location takes precedence.
amenitiesNoAmenities required in every result. Only listed enum values are supported. All-inclusive is not a supported filter; never promise that results satisfy it.
longitudeNoOptional longitude when already known.
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.
checkinDateNoRequired with checkoutDate unless the user explicitly requested tonight. Use YYYY-MM-DD.
destinationYesCity, neighborhood, airport, landmark, or other broad destination.
starRatingsNoExact accepted hotel star classifications.
user_localeNoOptional traveler locale from the Claude client context, such as en-US. Omit if unavailable; do not infer it from the hotel destination.
checkoutDateNoRequired with checkinDate unless the user explicitly requested tonight. Use YYYY-MM-DD.
childrenAgesNoWhole-number ages from 0 to 17 for every child at check-in, up to 8 children. The array length must equal children.
maximumPriceNoMaximum nightly price in the selected currency.
minimumPriceNoMinimum nightly price in the selected currency.
propertyTypesNoProperty category search. Supported canonical categories: hotel, motel, resort, hostel, apartment, apart-hotel, extended-stay, condo, studio, house, townhome, guesthouse, bed-and-breakfast, villa, cabin, cottage, campground, rv, estate, boat, chateau, hotel-suites, corporate-apartment, farm-house, lodge, barn, mobile-home, house-boat, castle, mas, tower, mill, building. Mappings: chalet -> cabin; inn -> hotel. These broader categories can contain other subtypes; explain the mapping and do not promise exact-subtype matches. Other unknown types return a normal unsupported-search explanation, not a tool error.
minimumStarRatingNoMinimum hotel star classification from 1 to 5; distinct from guest review score.
minimumReviewScoreNoMinimum guest review score out of 10; distinct from hotel star classification.
user_location_cityNoOptional approximate traveler city supplied by the Claude client. Omit if unavailable; this is not the hotel destination.
freeCancellationOnlyNoWhether results require free cancellation or refundable rates.
user_location_regionNoOptional traveler state or region supplied by the Claude client. Omit if unavailable; do not infer it from the hotel destination.
user_location_countryNoOptional two-letter traveler country supplied by the Claude client, such as US. Omit if unavailable; do not infer it from the hotel destination.
user_location_timezoneNoOptional IANA timezone of the traveler supplied by the Claude client. Omit if unavailable; this does not set the hotel's local stay dates.

Output Schema

NameRequiredDescriptionDefault
pageYes
totalYes
searchYes
statusNo
messageNo
totalPagesYes
requiredInputNo
accommodationsYes
filterMappingsNo
priceDisclosureYes
unsupportedFiltersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / unsupportedFilters
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "field": {
      +        "enum": [
      +          "sort",
      +          "propertyTypes",
      +          "amenities"
      +        ],
      +        "type": "string"
      +      },
      +      "values": {
      +        "items": {
      +          "type": "string"
      +        },
      +        "type": "array"
      +      }
      +    },
      +    "required": [
      +      "field",
      +      "values"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  2. Changed15 schema fields changed
    • changedInput schema / properties / amenities / description
      Previous value: -"Amenities required in every result."New value: +"Amenities required in every result. Only listed enum values are supported. All-inclusive is not a supported filter; never promise that results satisfy it."
    • addedInput schema / properties / amenities / items / anyOf
      Added value: +[
      +  {
      +    "enum": [
      +      "pool",
      +      "parking",
      +      "wifi",
      +      "free-wifi",
      +      "kitchen",
      +      "fireplace",
      +      "beachfront",
      +      "washer",
      +      "dryer",
      +      "air-conditioning",
      +      "tv",
      +      "heating",
      +      "family-friendly",
      +      "kids-friendly",
      +      "pet-friendly",
      +      "hot-tub",
      +      "free-breakfast",
      +      "free-cancellation",
      +      "laundry-in-unit",
      +      "laundry-on-site",
      +      "accessible",
      +      "for-couples",
      +      "solarium",
      +      "long-term-deals",
      +      "pay-over-time",
      +      "accept-local"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "maxLength": 100,
      +    "type": "string"
      +  }
      +]
    • removedInput schema / properties / amenities / items / enum
      Removed value: -[
      -  "pool",
      -  "parking",
      -  "wifi",
      -  "free-wifi",
      -  "kitchen",
      -  "fireplace",
      -  "beachfront",
      -  "washer",
      -  "dryer",
      -  "air-conditioning",
      -  "tv",
      -  "heating",
      -  "family-friendly",
      -  "kids-friendly",
      -  "pet-friendly",
      -  "hot-tub",
      -  "free-breakfast",
      -  "free-cancellation",
      -  "laundry-in-unit",
      -  "laundry-on-site",
      -  "accessible",
      -  "for-couples",
      -  "solarium",
      -  "long-term-deals",
      -  "pay-over-time",
      -  "accept-local"
      -]
    • removedInput schema / properties / amenities / items / type
      Removed value: -"string"
    • changedInput schema / properties / propertyTypes / description
      Previous value: -"Accepted accommodation types, such as hotel, motel, resort, hostel, or apartment."New value: +"Property category search. Supported canonical categories: hotel, motel, resort, hostel, apartment, apart-hotel, extended-stay, condo, studio, house, townhome, guesthouse, bed-and-breakfast, villa, cabin, cottage, campground, rv, estate, boat, chateau, hotel-suites, corporate-apartment, farm-house, lodge, barn, mobile-home, house-boat, castle, mas, tower, mill, building. Mappings: chalet -> cabin; inn -> hotel. These broader categories can contain other subtypes; explain the mapping and do not promise exact-subtype matches. Other unknown types return a normal unsupported-search explanation, not a tool error."
    • addedInput schema / properties / propertyTypes / items / anyOf
      Added value: +[
      +  {
      +    "enum": [
      +      "hotel",
      +      "motel",
      +      "resort",
      +      "hostel",
      +      "apartment",
      +      "apart-hotel",
      +      "extended-stay",
      +      "condo",
      +      "studio",
      +      "house",
      +      "townhome",
      +      "guesthouse",
      +      "bed-and-breakfast",
      +      "villa",
      +      "cabin",
      +      "cottage",
      +      "campground",
      +      "rv",
      +      "estate",
      +      "boat",
      +      "chateau",
      +      "hotel-suites",
      +      "corporate-apartment",
      +      "farm-house",
      +      "lodge",
      +      "barn",
      +      "mobile-home",
      +      "house-boat",
      +      "castle",
      +      "mas",
      +      "tower",
      +      "mill",
      +      "building",
      +      "chalet",
      +      "inn"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "maxLength": 100,
      +    "type": "string"
      +  }
      +]
    • removedInput schema / properties / propertyTypes / items / enum
      Removed value: -[
      -  "hotel",
      -  "motel",
      -  "resort",
      -  "hostel",
      -  "apartment",
      -  "apart-hotel",
      -  "extended-stay",
      -  "condo",
      -  "studio",
      -  "house",
      -  "townhome",
      -  "guesthouse",
      -  "bed-and-breakfast",
      -  "villa",
      -  "cabin",
      -  "cottage",
      -  "campground",
      -  "rv",
      -  "estate",
      -  "boat",
      -  "chateau",
      -  "hotel-suites",
      -  "corporate-apartment",
      -  "farm-house",
      -  "lodge",
      -  "barn",
      -  "mobile-home",
      -  "house-boat",
      -  "castle",
      -  "mas",
      -  "tower",
      -  "mill",
      -  "building"
      -]
    • removedInput schema / properties / propertyTypes / items / type
      Removed value: -"string"
    • addedInput schema / properties / sort / anyOf
      Added value: +[
      +  {
      +    "enum": [
      +      "top-picks",
      +      "distance",
      +      "total",
      +      "total-desc",
      +      "reviews"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "maxLength": 100,
      +    "type": "string"
      +  }
      +]
    • changedInput schema / properties / sort / description
      Previous value: -"Result order: top-picks, distance, total price ascending, total price descending, or guest reviews."New value: +"Use top-picks for recommended, distance for nearest, total for price ascending, total-desc for price descending, and reviews for guest review score (not hotel stars). Aliases: price_low_to_high / total price ascending -> total; price_high_to_low / total price descending -> total-desc; rating / guest reviews -> reviews. Unknown sorting returns normal correction guidance."
    • removedInput schema / properties / sort / enum
      Removed value: -[
      -  "top-picks",
      -  "distance",
      -  "total",
      -  "total-desc",
      -  "reviews"
      -]
    • removedInput schema / properties / sort / type
      Removed value: -"string"
    • addedOutput schema / properties / filterMappings
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "message": {
      +        "type": "string"
      +      },
      +      "requestedType": {
      +        "type": "string"
      +      },
      +      "searchType": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "requestedType",
      +      "searchType",
      +      "message"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / properties / requiredInput / items / enum
      Previous value: -[
      -  "checkinDate",
      -  "checkoutDate",
      -  "destination",
      -  "adults",
      -  "children",
      -  "childrenAges",
      -  "rooms",
      -  "roomArrangements"
      -]New value: +[
      +  "checkinDate",
      +  "checkoutDate",
      +  "destination",
      +  "adults",
      +  "children",
      +  "childrenAges",
      +  "rooms",
      +  "roomArrangements",
      +  "sort",
      +  "propertyTypes",
      +  "amenities"
      +]
    • changedOutput schema / properties / status / enum
      Previous value: -[
      -  "stay_dates_required",
      -  "stay_dates_invalid",
      -  "destination_not_found",
      -  "occupancy_invalid"
      -]New value: +[
      +  "stay_dates_required",
      +  "stay_dates_invalid",
      +  "destination_not_found",
      +  "occupancy_invalid",
      +  "filters_invalid"
      +]
  3. Changed23 schema fields changed
    • changedInput schema / properties / adults / description
      Previous value: -"Total adult guests. When omitted, Brek defaults to 2 adults per room."New value: +"Whole-number total adult count from 1 to 10 across all rooms. When omitted, Brek defaults to 2 adults per room."
    • 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 / children / description
      Previous value: -"Total child guests; when omitted, uses childrenAges.length."New value: +"Whole-number total child count from 0 to 8; when omitted, uses childrenAges.length."
    • removedInput schema / properties / children / maximum
      Removed value: -8
    • removedInput schema / properties / children / minimum
      Removed value: -0
    • changedInput schema / properties / children / type
      Previous value: -"integer"New value: +"number"
    • changedInput schema / properties / childrenAges / description
      Previous value: -"Age of every child at check-in. The array length must equal children."New value: +"Whole-number ages from 0 to 17 for every child at check-in, up to 8 children. The array length must equal children."
    • 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 / rooms / description
      Previous value: -"Number of rooms. Each room receives the default of 2 adults when adults is omitted."New value: +"Whole-number room count from 1 to 3. Each room receives the default of 2 adults when adults is omitted."
    • 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"
    • changedOutput schema / properties / requiredInput / items / enum
      Previous value: -[
      -  "checkinDate",
      -  "checkoutDate",
      -  "destination"
      -]New value: +[
      +  "checkinDate",
      +  "checkoutDate",
      +  "destination",
      +  "adults",
      +  "children",
      +  "childrenAges",
      +  "rooms",
      +  "roomArrangements"
      +]
    • changedOutput schema / properties / search / properties / adults / type
      Previous value: -"integer"New value: +"number"
    • changedOutput schema / properties / search / properties / children / type
      Previous value: -"integer"New value: +"number"
    • changedOutput schema / properties / search / properties / childrenAges / items / type
      Previous value: -"integer"New value: +"number"
    • changedOutput schema / properties / search / properties / rooms / type
      Previous value: -"integer"New value: +"number"
    • changedOutput schema / properties / status / enum
      Previous value: -[
      -  "stay_dates_required",
      -  "stay_dates_invalid",
      -  "destination_not_found"
      -]New value: +[
      +  "stay_dates_required",
      +  "stay_dates_invalid",
      +  "destination_not_found",
      +  "occupancy_invalid"
      +]
  4. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, so the safety profile is covered. The description adds what the annotations cannot: the ordered-list return shape (property IDs, facts, wholesale prices or bands, public-rate comparisons, Brek links) and an explicit anti-hallucination rule about never shortening or substituting propertyId. It doesn't discuss rate limits or failure modes, which keeps it below 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.

Conciseness4/5

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

It is long but dense and front-loaded: purpose first, then date prerequisite, then capabilities, then return shape, then follow-up routing. Nearly every sentence carries a distinct instruction. It could be tightened slightly by folding the multi-sentence ID-handling block, but nothing is redundant filler.

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?

This is a 27-parameter search tool with an output schema and full annotations, and the description is complete for calling it correctly — when to refuse, which filters exist, what comes back, and how to chain into the sibling tools. No gap remains that would cause a mis-call.

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 description coverage is 96%, so the baseline is 3 and the schema does the heavy lifting for all 27 parameters. The description still adds value by grouping the supported filter families (occupancy, price range, star rating, guest score, property types, amenities, cancellation preference, sort order) and by framing the checkinDate/checkoutDate/dateIntent relationship as a decision rule rather than a field doc.

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 gives a specific verb and resource (search/compare multiple hotels) plus the accepted destination granularities. The closing sentence explicitly excludes room-level offers for a single property, which cleanly separates it from get_accommodation_offers.

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 states hard preconditions (both dates required, or dateIntent=tonight only on an explicit 'tonight' request), explicitly forbids the agent from inventing dates, and names the escalation path (ask the user). It also routes single-match follow-ups to get_accommodation_details / get_accommodation_offers and tells the agent to disambiguate when several hotels match.

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