Skip to main content
Glama

Buscar casas libres en Varadero

buscar_casas
Read-only

Busca casas de renta verificadas en Varadero, Cuba, libres entre dos fechas y con sitio para las personas indicadas. Devuelve precio por noche en USD, capacidad y cómo se reserva cada una.

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": {
      "llegada": "<llegada>",
      "salida": "<salida>",
      "personas": "<personas>"
    },
    "name": "buscar_casas"
  }
}

Input Schema

NameRequiredDescriptionDefault
idiomaNoIdioma de los textos; por defecto es
salidaYesFecha de salida, AAAA-MM-DD
llegadaYesFecha de llegada, AAAA-MM-DD
personasYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/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 is covered; the description adds useful context by specifying that results are verified listings and what each result contains (nightly price in USD, capacity, booking method). It does not disclose result limits, pagination, or availability-staleness behavior.

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?

Two sentences, front-loaded with what is searched and under what constraints, followed by the return payload. No filler wording; every clause carries information.

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 no output schema, the description usefully summarizes the returned fields, and annotations cover the read-only nature. Minor gaps remain around result count/pagination and whether only verified listings are ever returned, but nothing critical for correct invocation is missing.

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 75%, so most parameters are already documented in the schema. The description clarifies that llegada/salida define a free-night window and that personas must fit the capacity, but adds no format or constraint detail (e.g., date format, max party size) beyond the schema.

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 ("Busca") and resource ("casas de renta verificadas en Varadero, Cuba") plus the availability constraints (dates, capacity). It is clearly a search tool, but it never names or contrasts itself with siblings such as ver_casa or pedir_reserva, leaving differentiation implicit.

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?

The availability-window framing implies when to use it (searching before booking), and the phrase "cómo se reserva cada una" hints at the downstream booking flow, but there is no explicit when-to-use/when-not-to-use statement or named alternative.

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