Burs-IA Utils

¿Es festivo en Colombia?

co-is-holiday

Read-onlyIdempotent

Indica si una fecha es festivo nacional en Colombia (con nombre), fin de semana y si es día hábil. Cuándo: hay que aplicar con exactitud una regla colombiana (DIAN, festivos de la Ley Emiliani, montos en COP, IVA, GMF, UVT), p. ej. al facturar o cobrar. No para: listar los 18 festivos nacionales de Colombia de un año, aplicando la Ley Emiliani (co-holidays). Efectos secundarios: ninguno (solo lectura, sin red, sin estado guardado). Determinista: la misma entrada da la misma salida. Límites: entrada JSON de hasta 64 KB, 1 s por llamada, resultado de hasta 1 MB.

EN: Says whether a date is a Colombian national holiday (with its name), a Sunday or Saturday, and whether it is a business day (Monday-Friday, or Monday-Saturday if saturday_is_business). When: a Colombian rule (DIAN, Ley Emiliani holidays, COP amounts, IVA, GMF, UVT) has to be applied exactly, e.g. in invoicing or payment flows. [EN completo / full EN: inputSchema.description]

Input Schema

Name	Required	Description	Default
`date`	Yes	YYYY-MM-DD (string; required; up to 10 chars; format date).
`saturday_is_business`	No	Treat Saturday as a business day (boolean; optional; default false).

Output Schema

Name	Required	Description	Default
`date`	No
`holiday`	No
`name_en`	No
`name_es`	No
`weekday`	No
`business_day`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026
- addedInput schema / properties / date / examples
```
Added value: +[
+  "2026-11-16"
+]
```

Changed1 schema field changedNov 1, 2026

addedInput schema / description

Added value: +"EN: Says whether a date is a Colombian national holiday (with its name), a Sunday or Saturday, and whether it is a business day (Monday-Friday, or Monday-Saturday if saturday_is_business). When: a Colombian rule (DIAN, Ley Emiliani holidays, COP amounts, IVA, GMF, UVT) has to be applied exactly, e.g. in invoicing or payment flows. Not for: listing the 18 Colombian national holidays for a year, applying Ley 51 de 1983 (co-holidays). Side effects: none (read-only, no network access, no stored state). Deterministic: the same input gives the same output. Limits: JSON input up to 64 KB, 1 s per call, result up to 1 MB."

First observedNov 1, 2026

TDQS

A4.7/5.0

Behavior5/5

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

While annotations cover read-only status, the description adds rich, necessary behavioral context that annotations omit: stating it is 'sin red, sin estado guardado' (no network, no stored state), deterministic, and specifying operational limits (64KB input, 1s call time).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The information is front-loaded and logically structured, moving from function to practical use (When), limitations (Not for), and operational constraints (Side effects). No language is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the specialized nature of Colombian regulatory compliance (DIAN, Ley Emiliani), the description is complete. It defines the scope, jurisdiction, and technical limitations necessary for correct deployment.

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?

Since schema description coverage is 100%, the schema already documents the parameters thoroughly. The description does not add semantic meaning to the parameters beyond what is already structurally defined. This meets the baseline score for comprehensive schema coverage.

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 definition explicitly states the tool checks if a date is a Colombian national holiday, weekend, or business day. Crucially, it distinguishes itself from related tools like co-holidays by stating it is not for listing all holidays.

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

Usage Guidelines5/5

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

It provides extremely specific use cases for invocation: when 'a Colombian rule... has to be applied exactly, e.g. in invoicing or payment flows.' It also provides an explicit exclusion: 'Not for: listing the 18 Colombian national holidays.'

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

All Burs-IA Utils tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?