Burs-IA Utils

Próximas ejecuciones de cron

cron-next-runs

Read-onlyIdempotent

Lista las próximas N ejecuciones (≤ 50) de una expresión cron después de un instante, en una zona horaria IANA. Cuándo: un resultado de fechas, zonas horarias o calendario tiene que ser exacto (desfases, horario de verano, fines de mes, bisiestos). No para: validar una expresión cron de 5 campos y la describe en inglés y español, con los valores expandidos (cron-explain). 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: Lists the next N (≤ 50) run times of a 5-field cron expression after a given instant, evaluated in an IANA time zone (DST-aware; non-existent local times are skipped). Searches at most 8 years ahead. When: a date, time-zone or calendar result has to be exact (offsets, daylight saving, month ends, leap years). Not for: validating a 5-field cron expression (cron-explain). [EN completo / full EN: inputSchema.description]

Input Schema

Name	Required	Description	Default
`after`	Yes	Start instant (exclusive) (string; required; up to 40 chars).
`count`	No	How many runs (integer; optional; default 5; min 1; max 50).
`timezone`	No	IANA time zone, e.g. America/Bogota (default UTC) (string; optional; default "UTC"; up to 64 chars).	UTC
`expression`	Yes	Cron expression (string; required; up to 200 chars).

Output Schema

Name	Required	Description	Default
`runs`	No
`runs_utc`	No
`timezone`	No
`expression`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 2, 2026
- addedInput schema / properties / after / examples
```
Added value: +[
+  "2026-10-30T10:00:00-05:00"
+]
```
- addedInput schema / properties / expression / examples
```
Added value: +[
+  "30 9 * * 1-5"
+]
```

Changed1 schema field changedNov 1, 2026

addedInput schema / description

Added value: +"EN: Lists the next N (≤ 50) run times of a 5-field cron expression after a given instant, evaluated in an IANA time zone (DST-aware; non-existent local times are skipped). Searches at most 8 years ahead. When: a date, time-zone or calendar result has to be exact (offsets, daylight saving, month ends, leap years). Not for: validating a 5-field cron expression (cron-explain). 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.8/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent, non-open-world, non-destructive, but the description adds real behavioral detail beyond them: DST-aware evaluation, skipping of non-existent local times, an 8-year search horizon, no network access, determinism, and concrete limits (64 KB input, 1 s/call, 1 MB result).

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 block is tight, front-loaded and every clause earns its place (purpose, when, not-for, side effects, limits). The bilingual duplication of content in the EN paragraph costs some conciseness, but structure and ordering remain clear.

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?

With an output schema present, an agent needs no description of return values, and the description fully covers inputs constraints, evaluation semantics (DST, 8-year horizon), safety profile and resource limits. Nothing needed 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.

Parameters4/5

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

Schema coverage is 100%, so baseline is 3; however the description adds meaning beyond the schema by specifying the 5-field constraint on the expression, the ≤ 50 cap on count, and that the timezone is IANA and DST-aware. It stops short of restating the exclusive-'after' semantics, hence 4.

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+resource ('Lists the next N run times of a 5-field cron expression') with scope qualifiers (≤ 50, after an instant, IANA time zone). It explicitly names the sibling it is not for (cron-explain), so an agent can distinguish the two without opening schemas.

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?

The 'Cuándo / When' clause gives the exact condition (a date, time-zone or calendar result that must be exact: offsets, DST, month ends, leap years) and the 'No para / Not for' clause routes validation requests to cron-explain. Both when-to-use and the alternative are explicit.

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?