Skip to main content
Glama

Tournride — Camino de Santiago bike rental

consultar_disponibilidad_bicicletas_camino

Consulta disponibilidad en tiempo real, PRECIOS EXACTOS (calculados con el motor de reservas: bici para los días + transporte ida + transporte vuelta + descuentos/promos activos como Early Bird) y tallas para rutas del Camino de Santiago. Devuelve MTB, E-bikes de gama alta (MTB eléctrica y trekking) y Gravel. Los modelos concretos, con su nombre, los devuelve la propia tool en available_models.

Pregunta al cliente lo que pide cada parámetro antes de llamar; no lo supongas. Usa SOLO los precios que devuelve la tool: no los estimes ni los recuerdes de otra consulta.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
finYesFecha de fin del alquiler (YYYY-MM-DD)
alturaNoALTURA del ciclista en cm. PREGUNTA la altura de CADA ciclista antes de llamar: es lo que determina la talla, y una talla mal elegida arruina el viaje.
inicioYesFecha de inicio del alquiler (YYYY-MM-DD)
puntoFinYesMUNICIPIO de devolución. PREGÚNTALO si no lo sabes (Ej: Santiago de Compostela, León...). Si la ruta acaba en Santiago, ofrece la devolución en la tienda Tournride de Santiago como la opción más fácil y SIN COSTE.
seleccionNoCesta de modelos para el precio exacto del grupo. PREGUNTA si quieren TODOS el mismo modelo o modelos DISTINTOS y, si son distintos, qué modelo cada persona. Cada item: {model_id|model, unidades}.
puntoInicioYesMUNICIPIO de entrega. PREGÚNTALO si no lo sabes (Ej: Saint Jean Pied de Port, Roncesvalles, Burgos...). Si el cliente solo sabe el hotel o alojamiento, pregunta en qué municipio está: el transporte se calcula por municipio.

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?

With no annotations, the description carries the full burden and does well: it discloses that prices are computed by the reservation engine (bike days + outbound transport + return transport + active promos like Early Bird), that it returns MTB/E-bike/Gravel categories, and that concrete models arrive in available_models. It also warns against estimating or caching prices, a meaningful behavioral constraint. It stops short of stating the operation is read-only or what permissions it needs.

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?

Front-loaded with the core verb and returned value, then a short imperative block. Mostly economical, though the second paragraph repeats the 'ask the client' theme and the exact-price emphasis already made in the opening.

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?

No output schema exists, so the description must carry return-value context, and it does name the key field (available_models) plus the bike categories and price composition. Combined with 100% schema coverage for the six params, an agent has enough to call it, though output shape is only partially described.

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% and the schema already embeds rich per-parameter instructions (altura, puntoInicio, puntoFin, seleccion). The description adds no syntax or format detail beyond that, so the baseline 3 applies; its parameter-related content is generic 'ask the client' guidance.

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 (Consulta) and resource (disponibilidad bicicletas) scoped to Camino de Santiago routes, and enumerates the returned value (real-time availability, exact prices, sizes, bike categories). It does not explicitly distinguish itself from the sibling crear_presupuesto_alquiler_camino, despite overlapping on pricing, so an agent must infer the read-vs-create split.

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?

Offers operational guidance ('pregunta al cliente lo que pide cada parámetro', 'usa SOLO los precios que devuelve la tool'), which steers invocation behavior. However, it never states when to call this tool versus the sibling budget tool, nor any exclusions, so tool selection is left implicit.

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