Chato — Control de asistencia por WhatsApp

Dar de alta un sitio

dar_de_alta_sitio

Crea un sitio (obra, sucursal, cliente, puesto) con su ubicación, su radio permitido y su horario de entrada y salida. La dirección se geocodifica; también se aceptan latitud y longitud. Úsala cuando el usuario quiera agregar una obra, un cliente nuevo o una sede. Create a site with its geofence and schedule.

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": {
      "nombre": "<nombre>"
    },
    "name": "dar_de_alta_sitio"
  }
}

Input Schema

Name	Required	Description
`dias`	No	Días laborables como números ISO: 1 lunes … 7 domingo. Por defecto lunes a sábado.
`nombre`	Yes	Nombre del sitio, como lo conoce el equipo ("Obra Apodaca", "Plaza Fiesta", "Caseta norte").
`empresa`	No	Nombre de la empresa. Solo hace falta cuando el usuario tiene varias empresas en Chato.
`entrada`	No	Hora de entrada (apertura de la ventana), HH:MM. Por defecto 06:00.
`latitud`	No	Latitud, si ya se conoce.
`radio_m`	No	Radio permitido en metros alrededor del sitio. Por defecto 150; usa más en obras grandes o plazas.
`longitud`	No	Longitud, si ya se conoce.
`direccion`	No	Dirección completa (calle, número, colonia, ciudad). Se usa para ubicar el sitio.
`salida_desde`	No	Desde qué hora se acepta la salida, HH:MM. Por defecto 12:00.
`salida_hasta`	No	Hasta qué hora se acepta la salida, HH:MM. Por defecto 19:00.
`entrada_hasta`	No	Hasta qué hora se acepta la entrada, HH:MM. Por defecto 10:00.
`recordatorios`	No	Encender los recordatorios de entrada y salida por WhatsApp. Por defecto apagados.
`retardo_despues_de`	No	A partir de qué hora la entrada cuenta como retardo, HH:MM. Por defecto 08:10.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare a non-readOnly, non-destructive, non-idempotent write. The description adds that the address is geocoded and that latitude/longitude are also accepted, which is useful behavioral context. It does not explain duplicate handling, failure modes, or any side effects of creating reminders.

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 short and front-loads the creation purpose, geocoding behavior, and usage cue. The final English sentence is redundant with the rest of the description and slightly reduces conciseness.

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?

For a 13-parameter creation tool with no output schema, the description covers the core purpose and main behavior. However, it omits important context such as how location is resolved when neither address nor coordinates are supplied, and what happens on duplicates or validation failures.

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 every parameter is already documented in the input schema. The description reinforces location and schedule semantics, but adds little beyond what the schema already provides for the 13 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 states a specific verb and resource: 'Crea un sitio' and lists the site types (obra, sucursal, cliente, puesto) plus what it includes (ubicación, radio, horario). It does not explicitly contrast with sibling tools like sitios or actualizar_horario_de_sitio, so sibling differentiation is limited.

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?

It gives clear when-to-use guidance: 'Úsala cuando el usuario quiera agregar una obra, un cliente nuevo o una sede.' It does not name alternatives or state when not to use it, but the inclusion context is explicit.

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

All Chato — Control de asistencia por WhatsApp 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?