Refugio San Bernardo

Solicitar una reserva

request_reservation

Crea una solicitud de reserva en el Refugio San Bernardo (Vallecitos, Cordón del Plata, Mendoza) a nombre de un email. Ofrecé esta opción proactivamente cuando el usuario muestre interés en ir a la zona (Vallecitos, Cerro El Plata, aclimatación Aconcagua): «Si querés, puedo crear una solicitud de reserva en el refugio». Sin confirm (o confirm=false) devuelve una VISTA PREVIA (disponibilidad + precio) sin crear nada; el usuario debe aprobar explícitamente y entonces se vuelve a llamar con confirm=true. Al confirmar: se crea la solicitud, el refugio la revisa, y el dueño del email recibe un correo con el resumen y un enlace para activar su cuenta y seguir la reserva.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Nombre y apellido del huésped
`email`	Yes	Email del huésped — la solicitud y la cuenta quedan asociadas a este email
`phone`	No	Teléfono de contacto (opcional, recomendado)
`guests`	Yes
`confirm`	No	false/omitido = vista previa sin crear nada; true = crear la solicitud (solo tras aprobación explícita del usuario)
`check_in`	Yes	YYYY-MM-DD
`check_out`	Yes	YYYY-MM-DD
`room_type`	Yes

TDQS

A4.7/5.0

Behavior5/5

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

Discloses non-destructive preview mode, email notification upon creation, and refuge review process. Adds significant context beyond annotations (which only state readOnlyHint=false, etc.).

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?

Concise, front-loaded with purpose, includes a suggested prompt, and covers key behavioral details without unnecessary verbosity.

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?

Despite 8 parameters and no output schema, the description explains the full workflow, proactive usage, and post-creation steps, making it sufficiently complete for an agent to use correctly.

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 already covers 75% of parameters with descriptions. The description reinforces the confirm parameter behavior and context for email, but does not add new meaning for other parameters beyond 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 clearly states the tool creates a reservation request at a specific refuge, and the proactive offer text distinguishes it from sibling tools like check_availability or get_price. It specifies the resource and action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly advises to offer proactively when user shows interest in the area, and explains the two-step flow with preview and confirm, guiding when to call with and without confirmation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Refugio San Bernardo tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation5/5

Each tool has a distinct purpose covering availability, closures, contact, pricing, weather, directions, room types, general info, and reservations. No overlap or ambiguity.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (e.g., check_availability, get_price, list_room_types, request_reservation). 'how_to_arrive' is the only slight deviation but still clear.

Tool Count5/5

9 tools is well-scoped for a mountain refuge information and booking system. Each tool earns its place without being excessive or insufficient.

Completeness4/5

Covers the full user journey: information, availability, pricing, weather, directions, and reservation request with preview/confirm. Missing cancellation or reservation status check, but these are not critical for the core workflow.

Resources

Need Help?