Burs-IA Utils

Sumar días hábiles en Colombia

co-business-days-add

Read-onlyIdempotent

Suma o resta N días hábiles a una fecha usando los festivos de Colombia (plazos legales, facturas, SLA). 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: sumar o restar días hábiles, saltando fines de semana y festivos dados (business-days-add). 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: Adds or subtracts N business days (días hábiles) to a date using Colombian national holidays, e.g. for legal deadlines, invoices or SLA due dates. 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: adding or subtracting business days, skipping weekends and given holidays (business-days-add). [EN completo / full EN: inputSchema.description]

Input Schema

Name	Required	Description
`date`	Yes	YYYY-MM-DD (string; required; up to 10 chars; format date).
`days`	Yes	Business days (negative subtracts) (integer; required; min -5000; max 5000).
`saturday_is_business`	No	Saturday counts as business day (boolean; optional; default false).

Output Schema

Name	Required	Description	Default
`result`	No	any JSON value
`weekday`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 2, 2026
- addedInput schema / properties / date / examples
```
Added value: +[
+  "2026-10-30"
+]
```
- addedInput schema / properties / days / examples
```
Added value: +[
+  1
+]
```

Changed1 schema field changedNov 1, 2026

addedInput schema / description

Added value: +"EN: Adds or subtracts N business days (días hábiles) to a date using Colombian national holidays, e.g. for legal deadlines, invoices or SLA due dates. 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: adding or subtracting business days, skipping weekends and given holidays (business-days-add). 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.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context: no network access, no stored state, determinism, and hard limits (64 KB input, 1 s per call, 1 MB result). It does not explain error behavior, which keeps it below 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.

Conciseness3/5

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

The core is front-loaded and well structured with labeled Cuándo/No para/Límites sections, but the content is duplicated across ES and EN and ends with a meta artifact ('[EN completo / full EN: inputSchema.description]') that is not tool information. The 'No para' phrasing is also awkwardly worded, requiring a second read to see it points at the generic sibling.

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 an output schema present, return values need not be described, and annotations plus the limits/determinism notes cover behavior. Parameters are fully documented in the schema. The definition is complete enough to call correctly; only error/failure semantics are absent.

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 parameters (date, days, saturday_is_business) are documented in the schema with types, bounds and defaults. The description only restates 'N días' and the date concept, adding no syntax or edge-case meaning beyond the schema, so the baseline 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?

States a specific verb and resource ('Suma o resta N días hábiles a una fecha') plus the exact holiday basis (festivos de Colombia), and names the sibling it is not (business-days-add). An agent can distinguish it from the generic business-days-add without opening either schema.

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?

Explicit 'Cuándo' clause gives concrete triggers (DIAN, Ley Emiliani, COP, IVA, GMF, UVT, facturación/cobro) and an explicit 'No para' clause routes the generic case to business-days-add. Both when-to-use and when-not-to-use are stated.

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?