Skip to main content
Glama

Chato — Control de asistencia por WhatsApp

Guardias por puesto

guardias_por_puesto
Read-only

Calcula cuántas personas hacen falta para cubrir un puesto de vigilancia, limpieza o mantenimiento sin pasar la jornada máxima de la Ley Federal del Trabajo (46 h por semana en 2027, 44 en 2028, 42 en 2029, 40 en 2030), y el mínimo si se paga el máximo de horas extra. Úsala cuando alguien pregunte cuántos guardias, vigilantes o elementos necesita por puesto, caseta o turno, o cómo armar roles 24/7. How many guards or workers a 24/7 post needs under Mexican labor law.

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

Input Schema

NameRequiredDescriptionDefault
anioNoAño a evaluar (la jornada máxima baja cada año de 2027 a 2030). Por defecto 2027.
horas_por_diaNoHoras que el puesto está cubierto cada día (24 para un puesto permanente). Por defecto 24.
dias_por_semanaNoDías a la semana que se cubre el puesto. Por defecto 7.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 is covered. The description adds real context by grounding the calculation in a legal schedule (46/44/42/40 h from 2027 to 2030) and by saying it returns two figures: the minimum without exceeding the jornada and the minimum if maximum overtime is paid. It does not say anything about precision, rounding, or assumptions about shift patterns.

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 calculation is front-loaded in one long but well-built sentence, followed by the usage trigger and a short English restatement. The English line is somewhat redundant for a bilingual audience but earns its place for retrieval; otherwise there is little waste.

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 carries the return-value burden and does so adequately by naming the two computed numbers. All parameters are optional with defaults documented in the schema, so an agent can call it with zero arguments. Minor gap: it does not describe the shape of the result beyond the two figures.

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 each of the three parameters (anio, horas_por_dia, dias_por_semana) already carries a description and default. The description echoes the year ramp for anio, which reinforces but does not extend the schema; baseline 3 applies.

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?

States a precise verb and resource: it calculates headcount needed to cover a post (vigilancia, limpieza, mantenimiento) under the Ley Federal del Trabajo maxima, plus the minimum if overtime is paid. The scope is concrete enough to separate it from scheduling tools, though it never names the closest siblings (evaluar_turno, cobertura_de_sitio) to draw that line explicitly.

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 an explicit trigger phrase: 'Úsala cuando alguien pregunte cuántos guardias, vigilantes o elementos necesita por puesto, caseta o turno, o cómo armar roles 24/7.' That covers the main invocation context, but there is no guidance on when not to use it or which sibling to pick when the question is about an existing shift rather than required headcount.

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