Skip to main content
Glama

Enviar una solicitud de reserva

pedir_reserva

Envía al dueño la solicitud de reserva en nombre del usuario. NO es un pago ni una reserva cerrada: el dueño tiene 48 horas para aceptar o rechazar. Llama solo si el usuario ha leído los términos de ver_terminos y te ha dicho expresamente que los acepta; entonces pasa acepta_terminos = true. Necesitas su nombre real y su WhatsApp con código de país. Devuelve un enlace privado donde el usuario sigue el estado y, si el dueño acepta, ve su contacto para acordar el depósito directamente con él.

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": {
      "casa": "<casa>",
      "llegada": "<llegada>",
      "salida": "<salida>",
      "personas": "<personas>",
      "nombre": "<nombre>",
      "whatsapp": "<whatsapp>",
      "acepta_terminos": "<acepta_terminos>"
    },
    "name": "pedir_reserva"
  }
}

Input Schema

NameRequiredDescriptionDefault
casaYes
correoNoOpcional: para avisarle de la respuesta
idiomaNo
nombreYesNombre de quien se aloja
salidaYes
llegadaYes
personasYes
whatsappYesWhatsApp con código de país, por ejemplo +34 600 111 222
acepta_terminosYestrue solo si el usuario leyó y aceptó expresamente los términos

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, but the description adds substantive process behavior the annotations cannot convey: no payment is taken, the booking is not confirmed, the owner has 48 hours to accept or reject, and the response is a private tracking link that later reveals the owner's contact. The main omission is duplicate-submission behavior, which matters given idempotentHint=false and a required-terms gate.

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?

Three sentences, front-loaded with the negative definition first, then the gating condition, then the required inputs and return value. Every clause carries information an agent needs to decide whether and how to call.

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 non-idempotent write with no output schema, the description covers the essentials: preconditions, the human-approval window, and what the returned link is for. The remaining gap is operational detail on the date and occupancy parameters, whose formats and constraints are undocumented in both schema and text.

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 44%, so the description must carry weight; it does well on acepta_terminos, defining the exact condition under which true is legitimate, and it reinforces that nombre must be the real name and whatsapp must include a country code. However, six parameters (casa, llegada, salida, personas, correo, idioma) get no added meaning, and the date format for llegada/salida is left entirely ambiguous.

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?

States a specific verb and resource ('Envía al dueño la solicitud de reserva en nombre del usuario') and immediately draws the boundary against what an agent might assume it is ('NO es un pago ni una reserva cerrada'). That negative framing plus the reference to ver_terminos clearly separates it from siblings like estado_solicitud or ver_casa.

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?

Gives an explicit, checkable precondition: call only after the user has read the terms via ver_terminos and expressly accepted them, then set acepta_terminos = true. It also names the follow-up path (the private status link), so the agent knows this is the entry point of a multi-step flow rather than a one-off.

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