Skip to main content
Glama

Chato — Control de asistencia por WhatsApp

Quién no ha llegado

quien_no_ha_llegado
Read-only

Para un día (hoy por defecto) y por sitio: quién ya registró su entrada por WhatsApp (hora y minutos de retardo), quién todavía no registra aunque ya pasó su hora, y quién no tiene horario ese día. Es la pregunta de la mañana del supervisor: "¿quién falta en la obra?", "¿ya llegaron todos a Plaza X?", "¿quién llegó tarde hoy?". Who has not clocked in yet today, per site.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "quien_no_ha_llegado"
  }
}

Input Schema

NameRequiredDescriptionDefault
fechaNoFecha AAAA-MM-DD en la zona horaria de la empresa. Por defecto hoy.
sitioNoNombre del sitio (obra, sucursal, cliente). Por defecto todos.
empresaNoNombre de la empresa. Solo hace falta cuando el usuario tiene varias empresas en Chato.

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=true and openWorldHint=false, so the safety profile is covered and the description is free to add semantics: it explains that results are grouped into three states and that delay is reported in hours and minutes, and that the underlying signal is WhatsApp check-in. It does not discuss ordering, coverage limits, or what happens for employees assigned to multiple sites, which is why it is not a 5.

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 core sentence is dense but front-loaded with the per-day/per-site scope, and the example questions earn their place as intent-matching cues. The trailing English sentence is a near-duplicate of the opening for bilingual matching, which is mildly redundant but cheap given how much routing value it adds.

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?

With no output schema, the description usefully compensates by describing the three result categories and the delay unit, which is what an agent needs to interpret results. It is not fully complete: it does not say whether employees with no site assignment appear, how results are ordered, or what an empty day looks like.

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 all three parameters (fecha, sitio, empresa) are already documented with formats and defaults. The description only restates the defaults in prose ("hoy por defecto", "por sitio"), adding no new constraint or edge case such as timezone handling beyond what the schema says. Baseline 3 applies when the schema carries the load.

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 names the resource (attendance check-ins per site per day) and enumerates the three result buckets it returns: already clocked in with delay, overdue but not registered, and no schedule that day. That enumeration plus the sample supervisor questions ("¿quién falta en la obra?", "¿ya llegaron todos a Plaza X?") makes it distinguishable from a generic daily-attendance sibling without opening a 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?

Usage context is explicit and vivid: it is "la pregunta de la mañana del supervisor", with three concrete phrasings that tell the agent exactly which user intents should route here. It stops short of naming an alternative tool or stating when NOT to use it (e.g. vs. a general day-attendance or shift-evaluation tool), so it is strong context without exclusions.

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