Skip to main content
Glama

Fechas más baratas de una estancia

fechas_mas_baratas
Read-onlyIdempotent

Para fechas flexibles: busca las entradas más baratas de una estancia de N noches dentro de un rango (máximo 62 días), confirma el precio real y da el enlace de reserva. «Semana» = 7 noches.

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": {
      "desde": "<desde>",
      "hasta": "<hasta>",
      "noches": "<noches>",
      "habitaciones": "<habitaciones>"
    },
    "name": "fechas_mas_baratas"
  }
}

Input Schema

NameRequiredDescriptionDefault
desdeYesPrimer día posible de entrada, YYYY-MM-DD
hastaYesÚltimo día posible de salida, YYYY-MM-DD
idiomaNoIdioma de los textos y del enlace de reserva (por defecto es)
nochesYes
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.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive status, so the safety profile is covered. The description adds real behavioral value beyond that: a maximum 62-day search window, the fact that it confirms the actual price rather than an estimate, and that it returns a booking link. It does not mention latency, rate limits, or what happens when no cheap dates exist.

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, zero filler, with the use case front-loaded before the mechanics and the range constraint. Every clause carries information an agent needs.

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

Completeness5/5

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

For a six-parameter search tool with no output schema, the description covers the intent, the range limit, the pricing guarantee and the return payload (booking link). The remaining gaps, such as empty-result behavior, are minor against 83% schema coverage and full annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 83%, so the schema already carries most parameter meaning. The description nevertheless adds two things absent from the schema: the maximum 62-day span across «desde»/«hasta», and the interpretation rule «Semana» = 7 noches for the «noches» parameter, which prevents a common misreading.

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 states a specific verb and resource: it searches the cheapest check-in dates for an N-night stay within a range, confirms the real price, and returns a booking link. The framing «Para fechas flexibles» distinguishes it from a fixed-date availability lookup, 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 Guidelines4/5

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

The opening «Para fechas flexibles» gives a clear condition for selecting this tool over a date-specific search, and the 62-day ceiling bounds the request. It stops short of naming an alternative tool or stating exclusion cases, so it does not reach the top band.

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