Directorio Systema

Reservar cita / Book appointment

reservar_cita

ES: Reserva una cita REAL como invitado (nombre + teléfono). La confirmación llega por WhatsApp/SMS al teléfono dado. Usá consultar_disponibilidad primero para elegir hora y staffId. / EN: Books a REAL appointment as a guest (name + phone). Confirmation arrives via WhatsApp/SMS to the given phone. Use consultar_disponibilidad first to pick a time and staffId.

Input Schema

TableJSON Schema

Name	Required	Description
`hora`	Yes	Hora HH:MM (24h), de consultar_disponibilidad
`slug`	Yes	Slug del negocio (de buscar_negocios) / Business slug (from buscar_negocios)
`fecha`	Yes	Fecha YYYY-MM-DD
`notas`	No
`nombre`	Yes	Nombre del cliente / Customer name
`staffId`	No	staffId de consultar_disponibilidad (opcional: sin él se asigna el primer profesional con esa hora libre) / staffId from consultar_disponibilidad (optional: otherwise the first staff member free at that time is assigned)
`servicio`	Yes	Nombre del servicio / Service name
`telefono`	Yes	Teléfono del cliente (con código de país si es posible) / Customer phone
`direccion`	No	Dirección donde se presta el servicio, si es a domicilio (ver_negocio indica qué servicios lo son) / Address where the service is performed, for at-home services

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 5, 2026

addedInput schema / properties / direccion

Added value: +{
+  "description": "Dirección donde se presta el servicio, si es a domicilio (ver_negocio indica qué servicios lo son) / Address where the service is performed, for at-home services",
+  "maxLength": 300,
+  "type": "string"
+}

First observedAug 19, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations provided, the description carries the behavioral disclosure burden. It discloses that this is a REAL booking, that confirmation arrives via WhatsApp/SMS, and that it operates as a guest booking with name and phone. It does not mention irreversibility or duplicate-booking risks, but the main side effects are clearly communicated.

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?

The description is concise and front-loaded with the core action and inputs. The bilingual format adds slight redundancy, but both language blocks are short and each sentence carries meaningful information about the booking behavior and prerequisite.

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

Completeness3/5

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

The description gives the essential what, prerequisite, and confirmation channel, which is good for a booking tool. However, since there is no output schema, it does not describe what the tool returns on success or failure, and it does not mention cancellation or error scenarios, leaving some ambiguity for the agent.

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 89%, so the schema already documents most parameters. The description adds useful context that hora and staffId should come from consultar_disponibilidad and that confirmation goes to the given phone, but it does not systematically explain all 9 parameters.

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 clearly states the verb and resource: 'Books a REAL appointment as a guest' and specifies the required inputs (name + phone). It distinguishes that this is a real booking rather than a placeholder, though it does not explicitly contrast it with siblings like reservar_clase or reservar_habitacion.

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 description explicitly instructs the agent to use consultar_disponibilidad first to choose the time and staffId, which is key usage guidance. It does not, however, state when not to use this tool or compare it against alternative reservation tools.

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

All Directorio Systema tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?