Skip to main content
Glama

Chato — Control de asistencia por WhatsApp

Asistencia del día

asistencia_del_dia
Read-only

Detalle de un día por persona: hora de entrada y de salida, desde qué sitio, si fue retardo, falta, salida sin registrar o registro fuera de sitio, y horas trabajadas. Úsala para "¿cómo estuvo la asistencia ayer?", "¿a qué hora salió Juan?" o para revisar un día concreto. Daily attendance detail per employee.

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": "asistencia_del_dia"
  }
}

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

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered. The description adds value by listing the outcome categories the response will contain (retardo, falta, salida sin registrar, fuera de sitio, horas trabajadas), but says nothing about how missing or partial data is handled, whether hours are computed or stored, or any volume limits.

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?

Front-loads the returned data, then the usage triggers, in two tight sentences. The trailing English sentence is largely a translation of the first and is mildly redundant, though it aids bilingual matching.

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?

There is no output schema, but the description compensates by enumerating the fields the result will contain, and the input schema fully documents the three optional parameters. For a low-complexity, zero-required-parameter read tool this is close to sufficient; only edge-case behavior remains unstated.

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% and all three optional parameters document their defaults and formats (AAAA-MM-DD in company timezone, all sites by default, empresa only when multiple companies exist). The description adds no additional parameter meaning, so the baseline of 3 applies.

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?

Names a specific resource and scope: per-person detail for a single day, and enumerates exactly what it reports (entrada/salida, sitio, retardo, falta, salida sin registrar, registro fuera de sitio, horas trabajadas). That level of field enumeration lets an agent distinguish it from raw-record siblings such as registro_de_jornada or quien_no_ha_llegado 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?

Gives concrete trigger questions ("¿cómo estuvo la asistencia ayer?", "¿a qué hora salió Juan?") plus the general case of reviewing a specific day, which is clear when-to-use guidance. It stops short of naming alternatives or stating when NOT to use it, so it does not reach the explicit routing level.

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