Skip to main content
Glama

Better Llama — Chile data

Feriados, días hábiles, comunas y validación de RUT (Chile)

chile_calendar_and_rut
Read-onlyIdempotent

Utilidades para Chile sin llamadas externas: feriados legales nacionales, regionales y comunales (2022-2035), si una fecha es feriado, días hábiles entre dos fechas, sumar N días hábiles a una fecha, regiones/provincias/comunas con código CUT, y validación o cálculo del dígito verificador del RUT. / Chile holidays, business days, communes and RUT validation.

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

Input Schema

NameRequiredDescriptionDefault
rutsNoRUT a validar — Formatos 12.345.678-5, 12345678-5 o 123456785. Máximo 5.000.
datesNoFechas a consultar (es_feriado) — Fechas AAAA-MM-DD. Vacío = hoy (hora de Chile).
yearsNoAños (feriados) — Años a listar (2022–2035). Vacío = año en curso. / Years.
comunaNoComuna — Nombre o código CUT (p. ej. Chillán o 16101). Aplica feriados comunales (20 de agosto en Chillán y Chillán Viejo).
regionNoRegión — Código (13), sigla (RM), ISO (CL-RM), numeral (XIII) o nombre. Filtra comunas/provincias y aplica feriados regionales.
searchNoBuscar por nombre (DPA) — Texto sin tildes ni mayúsculas, p. ej. 'nunoa'.
toDateNoHasta (AAAA-MM-DD) — Fin del rango, inclusive.
fromDateNoDesde (AAAA-MM-DD) — Inicio del rango (dias_habiles, o filtro de feriados).
maxItemsNoMáximo de resultados a devolver (1-1000). Por defecto 50.
operationNoOperación / Operation — Qué calcular.feriados
startDateNoFecha inicial (sumar_dias_habiles) — Vacío = hoy. Se cuenta desde el día siguiente.
includeBankNoIncluir feriado bancario (31 dic) — El 31 de diciembre es feriado solo para la atención bancaria.
rutBodyOnlyNoLos RUT vienen sin dígito verificador — Calcula el DV a partir del cuerpo.
businessDaysNoDías hábiles a sumar (negativo = restar) — Para sumar_dias_habiles.
includeRegionalNoIncluir feriados regionales en el listado — Si no indicas región, lista también los feriados regionales (marcados con scope=regional).
saturdayIsBusinessDayNoSábado es día hábil — Para plazos legales que cuentan sábados (p. ej. algunos plazos procesales).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent and non-destructive behavior, so the description adds value chiefly via 'sin llamadas externas' (fully offline, bundled data) and the 2022-2035 coverage window, both of which affect how an agent should trust and scope calls. Minor tension: the openWorldHint=true annotation sits uneasily beside the 'no external calls' claim; the description could have reconciled them. No return-format detail is offered, which matters for a multi-operation tool.

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 key selling point (offline, no external calls) then enumerates capabilities in a compact list, with a short English mirror line for cross-language agents. Every clause maps to an actual operation, though the kitchen-sink enumeration makes it longer than a single-purpose tool would need.

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 16-parameter, 8-operation bundler with no output schema, the definition covers purpose, data scope and offline nature, while the fully documented schema carries parameter semantics and per-operation applicability. Remaining gap is result shape: the agent does not learn from the description what a validar_rut versus feriados response 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% and each of the 16 parameters carries a substantive description, including format examples, ranges and per-operation applicability, so baseline 3 applies. The description itself adds essentially nothing parameter-level beyond restating that RUTs can be validated or completed to a check digit, work the schema already documents in detail.

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 concrete verbs and resources for every capability: legal/regional/communal holidays 2022-2035, holiday check, business days between dates, adding N business days, regions/provinces/communes with CUT codes, and RUT validation or check-digit calculation. An agent can tell from the description alone that this is a Chile calendar-and-identity utility, not one of the financial or news siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the enumeration of features plus the eight-value operation enum in the schema; parameter descriptions even mark which params apply to which operation (e.g. 'Para sumar_dias_habiles', 'Para dias_habiles'). What is missing is any explicit guidance on selecting between operations or on what to do when several data sets are needed at once, so the agent must infer routing from the schema alone.

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