Burs-IA Utils

Calendario del mes

calendar-month

Read-onlyIdempotent

Devuelve un mes como cuadrícula de semanas (inicio lunes o domingo) con números de semana ISO. Cuándo: un resultado de fechas, zonas horarias o calendario tiene que ser exacto (desfases, horario de verano, fines de mes, bisiestos). No para: describir un año y mes (month-info). 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: Returns a month as a grid of weeks (Monday or Sunday first) with ISO week numbers, suitable for rendering a calendar. When: a date, time-zone or calendar result has to be exact (offsets, daylight saving, month ends, leap years). Not for: describing a year and month (month-info). 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.

Input Schema

Name	Required	Description	Default
`year`	Yes	Year (integer; required; min 1; max 9999).
`month`	Yes	Month 1-12 (integer; required; min 1; max 12).
`week_start`	No	First day of week (optional; one of: monday, sunday; default "monday").	monday

Output Schema

Name	Required	Description	Default
`year`	No
`month`	No
`weeks`	No
`headers`	No
`week_start`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 2, 2026
- addedInput schema / properties / month / examples
```
Added value: +[
+  2
+]
```
- addedInput schema / properties / year / examples
```
Added value: +[
+  2026
+]
```
First observedNov 1, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations by stating no side effects (no network, no stored state), determinism, and hard limits (64 KB input, 1 s, 1 MB output). These are operational constraints an agent cannot derive from readOnlyHint/idempotentHint alone, so the extra context is genuinely valuable.

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-loaded with the core purpose, then cleanly sectioned into When / Not for / Side effects / Limits. Both Spanish and English versions are given, which is slightly redundant but each line carries distinct information.

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?

An output schema exists, so return-value explanation is unnecessary, and the description still covers side effects, determinism and execution limits. For a small pure-function calendar tool this leaves no material gap for correct invocation.

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%, so year, month and week_start (with enum and default) are already fully documented. The description only echoes the week-start choice and the ISO week numbering, adding no format or edge-case semantics beyond the schema. Baseline 3 is appropriate.

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 ('Devuelve un mes como cuadrícula de semanas') plus the distinguishing features (ISO week numbers) and explicitly names the sibling it is not, month-info. An agent can distinguish it from date-iso-week, month-info and calendar siblings without opening a 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?

Uses explicit 'Cuándo' and 'No para' sections, naming the alternative (month-info) and the condition that selects this tool (date/timezone results that must be exact). Nothing is left to inference.

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?