Skip to main content
Glama

Comparar precios entre hoteles

comparar_hoteles
Read-onlyIdempotent

Compara el precio más barato de la estancia en varios hoteles de Protur para las mismas fechas y huéspedes, ordenado de menor a mayor, con enlace de reserva de cada uno.

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": {
      "entrada": "<entrada>",
      "salida": "<salida>",
      "habitaciones": "<habitaciones>"
    },
    "name": "comparar_hoteles"
  }
}

Input Schema

NameRequiredDescriptionDefault
idiomaNoIdioma de los textos y del enlace de reserva (por defecto es)
salidaYesFecha de salida, YYYY-MM-DD
entradaYesFecha de entrada, YYYY-MM-DD
hotelesNoOpcional: slugs o nombres de los hoteles (por defecto, todos los que se reservan online)
habitacionesYesUna entrada por habitación

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is clear. The description adds that results are sorted ascending and include booking links, but does not cover other behavioral traits such as rate limits, authentication requirements, or handling of missing hotels.

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?

The description is a single, well-structured sentence that front-loads the core purpose and then adds key details (sorting, booking link). Every part earns its place with no unnecessary wording.

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 a tool with 5 parameters (3 required), no output schema, and rich annotations, the description covers the essential purpose and output format. It falls short only in not explicitly clarifying that the 'hoteles' parameter defaults to all online-bookable hotels, and in lacking guidance on when to choose this tool over siblings.

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 100%, so all parameters are documented in the schema. The description does not add meaning beyond what the schema provides; it only implies that dates and guest details are used, which is already evident from 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?

The description states a specific verb ('Compara'), resource ('precio más barato de la estancia en varios hoteles'), scope ('mismas fechas y huéspedes'), and output format ('ordenado de menor a mayor, con enlace de reserva'). This clearly distinguishes it from siblings like fechas_mas_baratas or disponibilidad, which likely serve different purposes.

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?

The description provides a clear usage context: comparing prices across multiple hotels for identical dates and guests. However, it does not explicitly state when to use this tool versus alternatives (e.g., fechas_mas_baratas or disponibilidad) or mention any exclusions or prerequisites.

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