Skip to main content
Glama

Disponibilidad y precios de un hotel

disponibilidad
Read-onlyIdempotent

Disponibilidad y precios reales de un hotel para unas fechas y unos huéspedes: tipos de habitación libres, tarifas, régimen, si se puede cancelar, y enlace para reservar directamente con esa búsqueda.

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

Input Schema

NameRequiredDescriptionDefault
hotelYesSlug o nombre del hotel (ver listar_hoteles)
idiomaNoIdioma de los textos y del enlace de reserva (por defecto es)
salidaYesFecha de salida, YYYY-MM-DD
entradaYesFecha de entrada, YYYY-MM-DD
habitacionesYesUna entrada por habitación

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 open-world, so the safety profile is covered. The description earns credit for disclosing return content (free room types, rates, board basis, cancellability, direct booking link) which is valuable since there is no output schema. It stops short of noting behavior when no availability exists or how pricing/currency is represented.

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?

A single front-loaded sentence with the resource and scope first, then the return payload. Dense and free of padding, though the trailing enumeration is long enough that it could be split for scannability.

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 read-only lookup with no output schema, the description covers the essentials: scope, inputs in general terms, and what the response contains. Missing only edge-case behavior (unavailable dates, unknown hotel slug) to be fully complete.

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 every parameter including the nested habitaciones array, child ages and language enum is already documented in the schema. The description only restates the date and guest scoping at a high level, adding no format or constraint detail beyond the schema; baseline 3 applies.

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?

States a specific verb-plus-resource purpose: real availability and prices for a hotel across given dates and guests, and enumerates what comes back (room types, rates, board, cancellation, booking link). This clearly separates it from descriptive siblings like ficha_hotel or info_hotel, though no sibling is named explicitly.

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 required date and occupancy inputs, so an agent can infer this is the tool for a concrete booking query. However, there is no explicit when-to-use or when-not guidance and no routing to alternatives such as fechas_mas_baratas or comparar_hoteles for adjacent needs.

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