Burs-IA Utils

Datos del mes y del año

month-info

Read-onlyIdempotent

Describe un año y mes: días, si es bisiesto, día de la semana del primero y del último, días entre semana y trimestre. Cuándo: un resultado de fechas, zonas horarias o calendario tiene que ser exacto (desfases, horario de verano, fines de mes, bisiestos). No para: devolver un mes como cuadrícula de semanas (calendar-month). 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: Describes a year and month: number of days, leap year, weekday of the first and last day, number of weekdays (Mon-Fri) and weekend days, and the quarter. When: a date, time-zone or calendar result has to be exact (offsets, daylight saving, month ends, leap years). Not for: returning a month as a grid of weeks (calendar-month). Side effects: none (read-only, no network access, no stored state). [EN completo / full EN: inputSchema.description]

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).

Output Schema

Name	Required	Description	Default
`days`	No
`quarter`	No
`weekdays`	No
`leap_year`	No
`last_weekday`	No
`weekend_days`	No
`first_weekday`	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
+]
```

Changed1 schema field changedNov 1, 2026

addedInput schema / description

Added value: +"EN: Describes a year and month: number of days, leap year, weekday of the first and last day, number of weekdays (Mon-Fri) and weekend days, and the quarter. When: a date, time-zone or calendar result has to be exact (offsets, daylight saving, month ends, leap years). Not for: returning a month as a grid of weeks (calendar-month). 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.6/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, and the description still adds value beyond them: no network access, no stored state, determinism guarantee, and concrete operational limits (64 KB input, 1 s per call, 1 MB result). That is exactly the extra behavioral context a calling agent needs.

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?

The Spanish version is front-loaded and well-sectioned (purpose, when, not for, side effects, determinism, limits). It loses a point for the bilingual duplication and the trailing meta-reference '[EN completo / full EN: inputSchema.description]', which adds length without adding 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?

A pure-function calendar tool with an output schema, full parameter documentation, annotations covering the safety profile, and stated limits — nothing an agent needs in order to call it correctly is missing.

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%, with both parameters carrying type, min/max and examples, so the schema does the heavy lifting. The description adds no syntax or edge-case guidance about year/month beyond what the schema already states, 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?

The description states a specific verb ('Describe') and resource ('un año y mes') and enumerates exactly what is returned: number of days, leap year, weekday of the first and last day, weekday/weekend counts, and quarter. It also names the sibling it is not (calendar-month), so an agent can distinguish it 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?

It gives an explicit 'Cuándo' condition (when a date, time-zone or calendar result must be exact – offsets, DST, month ends, leap years) and an explicit 'No para' exclusion that routes to calendar-month. Both the selection and rejection cases are covered.

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?