Skip to main content
Glama

Chato — Control de asistencia por WhatsApp

Cambiar el horario de un sitio

actualizar_horario_de_sitio
Idempotent

Cambia el horario de un sitio (hora de entrada, a partir de cuándo es retardo, ventana de salida, días laborables) o enciende y apaga sus recordatorios de WhatsApp. Solo cambia lo que se indique. Úsala para "cambia la entrada de la obra a las 7", "activa los recordatorios en Plaza Fiesta" o "la caseta ahora trabaja de lunes a domingo". Update a site schedule or reminders.

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": {
      "sitio": "<sitio>"
    },
    "name": "actualizar_horario_de_sitio"
  }
}

Input Schema

NameRequiredDescriptionDefault
diasNoDías laborables como números ISO: 1 lunes … 7 domingo.
sitioYesNombre del sitio.
empresaNoNombre de la empresa. Solo hace falta cuando el usuario tiene varias empresas en Chato.
entradaNoNueva hora de apertura de la entrada, HH:MM.
salida_desdeNoNueva hora desde la que se acepta la salida, HH:MM.
salida_hastaNoNueva hora límite de salida, HH:MM.
entrada_hastaNoNueva hora límite de entrada, HH:MM.
retardo_despues_deNoNueva hora a partir de la cual cuenta como retardo, HH:MM.
recordatorios_salidaNoEncender (true) o apagar (false) el recordatorio de salida.
recordatorios_entradaNoEncender (true) o apagar (false) el recordatorio de entrada.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, so the safety profile is covered. The description adds genuinely new behavioral context: unspecified fields are left untouched (partial mutation) and the same call also functions as a reminders on/off switch, which is not obvious from the schema alone. It does not discuss what happens if the site name is unknown or whether reminders require prior WhatsApp setup.

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 mutation scope is front-loaded in the first clause, followed by examples that earn their space by demonstrating intent. The trailing English sentence ("Update a site schedule or reminders.") merely repeats the Spanish opener and is the one piece of dead weight.

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 10-parameter partial-update tool with full schema coverage and annotations, the description covers what changes, what stays intact, and the reminder toggle. Minor gaps remain around failure modes (nonexistent site, ambiguous multi-company match) and whether other schedule fields exist that cannot be changed here.

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%, so the baseline is 3. The description restates the parameter groups in business language (entrada, a partir de cuándo es retardo, ventana de salida, días laborables, recordatorios) but adds no format, default, or constraint detail beyond what each schema property already documents.

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 opens with a specific verb and resource ("Cambia el horario de un sitio") and enumerates the concrete fields it can touch: hora de entrada, umbral de retardo, ventana de salida, días laborables, plus turning WhatsApp reminders on/off. That scope is clearly distinct from the creation/coverage siblings (dar_de_alta_sitio, cobertura_de_sitio), so an agent can tell what this tool does without opening the schema.

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?

Three concrete user-phrase examples ("cambia la entrada de la obra a las 7", "activa los recordatorios en Plaza Fiesta", "la caseta ahora trabaja de lunes a domingo") give strong when-to-use signal, and "Solo cambia lo que se indique" sets the partial-update expectation. It stops short of naming when NOT to use it or pointing to a sibling for related operations, so it is clear context rather than full routing guidance.

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