Burs-IA Utils

Días hábiles entre fechas

business-days-between

Read-onlyIdempotent

Cuenta días hábiles entre dos fechas, excluyendo fines de semana configurables y festivos. Cuándo: un resultado de fechas, zonas horarias o calendario tiene que ser exacto (desfases, horario de verano, fines de mes, bisiestos). No para: contar días hábiles entre dos fechas en Colombia, excluyendo domingos, sábados (co-business-days-between). 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: Counts working days between two dates, excluding configurable weekend days and a list of holidays. By default counts days after start up to and including end; inclusive counts both ends. When: a date, time-zone or calendar result has to be exact (offsets, daylight saving, month ends, leap years). Not for: counting business days (co-business-days-between). [EN completo / full EN: inputSchema.description]

Input Schema

Name	Required	Description
`end`	Yes	End date (string; required; up to 10 chars; format date).
`start`	Yes	Start date (string; required; up to 10 chars; format date).
`weekend`	No	Weekend days (0=Sun … 6=Sat) (array of integer; optional; default [0,6]; up to 6 items).
`holidays`	No	Holiday dates YYYY-MM-DD to skip (array of string; optional; default []; up to 2000 items).
`inclusive`	No	Count the start date too (boolean; optional; default false).

Output Schema

Name	Required	Description	Default
`business_days`	No
`holidays_skipped`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 2, 2026
- addedInput schema / properties / end / examples
```
Added value: +[
+  "2026-11-09"
+]
```
- addedInput schema / properties / start / examples
```
Added value: +[
+  "2026-11-02"
+]
```

Changed1 schema field changedNov 1, 2026

addedInput schema / description

Added value: +"EN: Counts working days between two dates, excluding configurable weekend days and a list of holidays. By default counts days after start up to and including end; inclusive counts both ends. When: a date, time-zone or calendar result has to be exact (offsets, daylight saving, month ends, leap years). Not for: counting business days (co-business-days-between). 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.4/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description still adds substance: no side effects, no network, no stored state, deterministic output, and hard limits (64 KB input, 1 s per call, 1 MB result). That is exactly the extra context annotations cannot carry.

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?

Front-loaded and each block is useful, but the full definition is duplicated in Spanish and English, and the ES 'No para' sentence is garbled ('contar días hábiles... en Colombia' reads as if it were the purpose). A truncated artifact ('[EN completo / full EN: inputSchema.description]') also appears inline.

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?

Output schema exists and all five parameters are documented, plus limits and determinism are stated, so an agent has enough to call it correctly. The confusing bilingual 'No para' phrasing and duplicated EN block are the only gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description earns more by explaining the counting convention (default counts days after start through end; inclusive counts both ends), which clarifies the `inclusive` flag beyond the schema's 'Count the start date too'.

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 ('Cuenta días hábiles entre dos fechas') plus the exclusion scope (configurable weekends and holidays). It also names the sibling it is not, so an agent can separate it from co-business-days-between 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 Guidelines4/5

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

Explicit 'Cuándo' and 'No para' sections, with the alternative co-business-days-between named for the Colombian case. The positive condition ('a date, time-zone or calendar result has to be exact') is somewhat generic and does not distinguish it from date-between or business-days-add, so it stops short of a 5.

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?