Skip to main content
Glama

agendar_yo_mismo

Para el DUEÑO: meter en Aisha una cita que le llegó por fuera.

Esta es la importante. Cuando a un negocio le hablan por teléfono, le escriben por WhatsApp o le llega alguien de la calle, esa cita debe entrar aquí igual que las de Aisha — si no, la agenda que ven los asistentes de IA está incompleta y pueden ofrecer una hora que ya está vendida.

A diferencia de crear_reserva, el contacto del cliente es OPCIONAL: el dueño lo tiene enfrente o acaba de hablar con él. Pero pídeselo si lo tiene a la mano, porque sirve para avisarle de cualquier cambio.

MUY IMPORTANTE — de quién es la cita: quien te está hablando es el DUEÑO del negocio, NO el cliente. Si no te dijo a nombre de quién va la cita, PREGÚNTASELO. No pongas el nombre de la persona con la que estás hablando, ni el del titular de la cuenta, ni ningún nombre que hayas deducido del contexto. Una cita a nombre equivocado es peor que no tenerla: el negocio llama a quien no es y pierde al que sí venía.

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": {
      "negocio": "<negocio>",
      "clave": "<clave>",
      "nombre_cliente": "<nombre_cliente>",
      "fecha": "<fecha>",
      "hora": "<hora>",
      "servicio": "<servicio>"
    },
    "name": "agendar_yo_mismo"
  }
}

Input Schema

NameRequiredDescriptionDefault
horaYes
claveYes
fechaYes
negocioYes
personaNo
servicioYes
nombre_clienteYes
contacto_clienteNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 disclose meaningful behavior: contacto_cliente is optional and why, and a critical semantic hazard (whose name goes on the appointment) with the failure mode spelled out. It does not state whether the slot is validated against existing bookings, what happens on conflict, or whether the caller must be the account owner — real gaps for a write tool, but far more than a bare 'create' would give.

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?

Key information is front-loaded ('Esta es la importante') and the identity warning is set apart with its own heading, which fits the high-stakes failure mode. It is somewhat long and the identity point is restated in three forms, which is defensible given the cost of error but not maximally economical.

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 output schema means return values needn't be described, and the highest-risk semantics (wrong client name) are covered thoroughly. But for an 8-parameter, 6-required mutation tool with zero annotation coverage, leaving 'clave' and 'persona' unexplained and saying nothing about conflict/availability handling leaves the definition short of complete.

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

Parameters2/5

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

Schema description coverage is 0% across 8 parameters, so the description must compensate and only partly does: it explains contacto_cliente's optionality and nombre_cliente's semantics in depth. 'clave' and 'persona' (default empty string) are never mentioned and are genuinely ambiguous, and negocio/servicio/fecha/hora get no format guidance.

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 first line names a specific actor, verb and resource: the OWNER inserting an externally-sourced appointment into Aisha. The following sentence makes the distinction from crear_reserva explicit (externally-captured vs. AI-booked), so an agent can route correctly without inspecting either schema.

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?

It enumerates the triggering situations (phone call, WhatsApp, walk-in) and states the consequence of misrouting (stale agenda, AI assistants selling already-booked slots). It also explicitly contrasts with crear_reserva on the one dimension that differentiates them (contacto_cliente optional here).

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