Skip to main content
Glama

Buscar hoteles

search_hotels
Read-onlyIdempotent

Search hotels on WizTrip (the same search as wiz-trip.com/hoteles). destination is a city name, an IATA code or a WizTrip destination id from find_destination. Returns hotels with stars, area, room, board, free cancellation and the WizTrip selling price of the whole stay in USD, each with url: its wiz-trip.com page, where the person books and pays. A price marked paquete_itinerario_wizzo includes the "Itinerario Wizzo" and is never the hotel alone.

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>",
      "check_in": "<check_in>",
      "check_out": "<check_out>"
    },
    "name": "search_hotels"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNo
boardNoRO room only, BB breakfast, HB half board, FB full board, AI all inclusive.
roomsNo
starsNo
adultsNo
check_inYesYYYY-MM-DD, from today (2026-11-19) on.
check_outYesYYYY-MM-DD, from today (2026-11-19) on.
destinationYesCity name, IATA code, or a G…/D… id from find_destination.
country_codeNoISO-2 country, to disambiguate the city.
children_agesNo
free_cancellationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / check_in / description
      Previous value: -"YYYY-MM-DD, from today (2026-11-18) on."New value: +"YYYY-MM-DD, from today (2026-11-19) on."
    • changedInput schema / properties / check_out / description
      Previous value: -"YYYY-MM-DD, from today (2026-11-18) on."New value: +"YYYY-MM-DD, from today (2026-11-19) on."
  2. Changed2 schema fields changed
    • changedInput schema / properties / check_in / description
      Previous value: -"YYYY-MM-DD, from today (2026-11-17) on."New value: +"YYYY-MM-DD, from today (2026-11-18) on."
    • changedInput schema / properties / check_out / description
      Previous value: -"YYYY-MM-DD, from today (2026-11-17) on."New value: +"YYYY-MM-DD, from today (2026-11-18) on."
  3. Changed2 schema fields changed
    • changedInput schema / properties / check_in / description
      Previous value: -"YYYY-MM-DD, from today (2026-11-16) on."New value: +"YYYY-MM-DD, from today (2026-11-17) on."
    • changedInput schema / properties / check_out / description
      Previous value: -"YYYY-MM-DD, from today (2026-11-16) on."New value: +"YYYY-MM-DD, from today (2026-11-17) on."
  4. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld=false, yet the description still adds real value: it enumerates what comes back (stars, area, room, board, free cancellation, whole-stay USD price), says each result has a `url` where the person books and pays, and warns that a paquete_itinerario_wizzo price bundles the itinerary. It omits result limits, defaults and pagination behavior, so not 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?

Four sentences, front-loaded with purpose and scope, then return shape, then the pricing caveat. Nothing is padded, though the final paquete_itinerario_wizzo sentence is dense and relies on domain jargon the agent must infer.

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 an 11-parameter, no-output-schema search tool the description does the important work: it explains the return payload and the booking URL, and clarifies the price semantics. The remaining gap is the absence of defaults, result-count limits and behavior for optional filters, which an agent would have to discover empirically.

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 only 45%, so the description carries part of the burden; it does explain the accepted `destination` formats (city, IATA, G/D id) and the currency/scope of the returned price. However, it says nothing about sort defaults, stars, rooms, adults, children_ages or free_cancellation, which remain undocumented outside the schema.

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 on WizTrip') and anchors it to a known surface ('the same search as wiz-trip.com/hoteles'). The hotel resource noun cleanly separates it from search_flights, search_activities and search_transfers without needing to name them.

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?

Gives clear routing guidance by tying `destination` to a WizTrip destination id from find_destination, which tells the agent a prerequisite lookup path. It does not state when to prefer this over alternatives or any exclusions, so it stops short of a full when/when-not statement.

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