Skip to main content
Glama

BookResorts — hotel & resort booking

Search hotels with live prices

search_hotels
Read-onlyIdempotent

Search hotels and resorts in a destination (city, region or resort area) with LIVE prices for the dates and party. Prices are totals for the whole stay in USD, taxes and fees included. Returns up to 15 hotels (cheapest first, or best-rated with sort=rating), with ids for get_hotel.

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>",
      "checkin": "<checkin>",
      "checkout": "<checkout>"
    },
    "name": "search_hotels"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoprice = cheapest first; rating = best guest rating firstprice
roomsNoNumber of rooms; adults/children are split across them
adultsNo
checkinYesYYYY-MM-DD
checkoutYesYYYY-MM-DD
min_starsNoOnly hotels with at least this star rating
destinationYese.g. 'Cancun', 'Punta Cana', 'Maui', 'Riviera Maya'
children_agesNoAges of children, if any
all_inclusive_onlyNo

Output Schema

NameRequiredDescriptionDefault
hotelsYes
summaryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "hotels": {
      +      "items": {
      +        "properties": {
      +          "boards": {
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "city": {
      +            "type": "string"
      +          },
      +          "country": {
      +            "type": "string"
      +          },
      +          "free_cancellation_available": {
      +            "type": "boolean"
      +          },
      +          "guest_rating": {
      +            "type": "number"
      +          },
      +          "hotel_id": {
      +            "type": "string"
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "page": {
      +            "description": "Hotel page with the dates, for the traveller",
      +            "type": "string"
      +          },
      +          "per_night_usd": {
      +            "type": "number"
      +          },
      +          "reviews": {
      +            "type": "integer"
      +          },
      +          "stars": {
      +            "type": "number"
      +          },
      +          "total_price_usd": {
      +            "type": "number"
      +          }
      +        },
      +        "required": [
      +          "hotel_id",
      +          "name",
      +          "total_price_usd",
      +          "page"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "summary": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "summary",
      +    "hotels"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Adds real context beyond the readOnly/openWorld annotations: prices are whole-stay totals in USD with taxes and fees included, results cap at 15, and default ordering is cheapest first. It does not mention price volatility, availability caveats, or auth/rate limits, so it is strong but not exhaustive.

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 tight sentences, front-loaded with the core action and scope, then pricing semantics, then result count and follow-up. No filler or repetition of 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?

With an output schema present, the description needn't explain return values in detail, and it still usefully covers result count, ordering, and the ids-to-get_hotel link. For a 9-parameter open-world search it is complete enough to call correctly, though a note on price availability/latency would close the last gap.

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 78%, so the schema already documents most parameters including sort, rooms, and min_stars. The description adds the party/date framing and the sort=rating behavior, but adds nothing about children_ages, all_inclusive_only, or the room/adult split beyond what the schema states. Baseline 3 applies when the schema does most of the work.

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 (search hotels and resorts) plus scope (destination, dates, party) and the distinguishing trait of live total pricing. It also names the sibling get_hotel as the follow-up consumer of the returned ids, which separates it from create_booking_link and get_hotel.

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?

Implies clearly when to use: when the agent needs candidate hotels with live prices for dates/party, and it signals the handoff to get_hotel via returned ids. It does not explicitly say when not to use it versus get_hotel or create_booking_link, so the alternative-selection guidance is implicit rather than stated.

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