Skip to main content
Glama

cancunhotels

Buscar hoteles en Cancún

buscar_hoteles
Read-only

Busca hoteles en Cancún y alrededores (Zona Hotelera, Costa/Playa Mujeres, Isla Mujeres, Riviera Cancún, Centro) por zona, tipo de viaje, sargazo, precio y estrellas. Search Cancún hotels by area, trip type, sargassum exposure, price and stars.

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

Input Schema

NameRequiredDescriptionDefault
zonaNoZona
textoNoTexto libre: nombre o palabra clave (p. ej. 'riu', 'parque acuático')
idiomaNoIdioma de la respuesta / response language (default es)
limiteNoMáximo de resultados (default 10)
familiasNo
solo_adultosNo
estrellas_minNo
frente_al_marNo
menos_sargazoNoSolo hoteles con exposición baja al sargazo
todo_incluidoNo
precio_max_mxnNoPrecio orientativo máximo por noche en MXN

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile and closed-world scope are covered by structured data. The description adds nothing behavioral beyond that: it does not say whether results are summary cards, how pricing is sourced/dated, whether the sargassum data is current, or what the caller should do next. It largely restates the search purpose.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The Spanish sentence is well front-loaded and efficient, but the entire content is then repeated verbatim in English, roughly doubling length without adding information. For a bilingual tool this may be intentional, yet a single-language opener plus distinct filter detail would have earned more of the space.

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

Completeness3/5

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

For an 11-parameter search tool with no output schema, the definition covers what can be filtered but not what comes back (result shape, whether prices/stars are included, pagination via limite) nor how to escalate to ficha_hotel or comparar_hoteles. It is adequate to invoke, but an agent must discover the result contract 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?

With 11 parameters and only 55% schema description coverage, the description must compensate, and it partially does by grouping filters into themes (zona, tipo de viaje, sargazo, precio, estrellas) that map onto zona, familias/solo_adultos, menos_sargazo, precio_max_mxn and estrellas_min. However, undocumented booleans such as frente_al_mar and todo_incluido get no meaning from either the schema or the description, so the compensation is incomplete.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete verb and resource ("Busca hoteles en Cancún") and enumerates the covered areas and the facets it searches on (zona, tipo de viaje, sargazo, precio, estrellas), so an agent knows exactly what the tool retrieves. It stops short of distinguishing itself from siblings such as comparar_hoteles or ficha_hotel, which would have earned a 5.

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

Usage Guidelines3/5

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

Usage is implied by the facet list — an agent can infer this is the discovery/search entry point — but there is no explicit when-to-use guidance, no mention of when NOT to use it, and no pointer to comparar_hoteles for comparisons or ficha_hotel for detail views. The exclusions are left entirely to inference.

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