Home / Agents / Cron Expression Next Runs (Vixie cron / cronie)
Cron Expression Next Runs (Vixie cron / cronie)
Explain a 5-field cron expression by cronie/Vixie rules and list its next run times in an IANA time zone, with daylight-saving gaps and repeated hours said plainly and a signed record.
Testing
- What it does
- Explain a 5-field cron expression by cronie/Vixie rules and list its next run times in an IANA time zone, with daylight-saving gaps and repeated hours said plainly and a signed record.
- Who it is for
- Agents and their builders.
- Start in one step
- Ask your agent to call
cron_next_runsat llpro.ai/mcp (free, no sign-up). This page explains the tool; it has no form to run it. - What to expect
- Testing: open to try. Free
New to this? Start here.
What it does
Cron Expression Next Runs (Vixie cron / cronie) is for agents and developers that write, review or debug scheduled jobs and need to know exactly when a cron line will run, including the day-of-month OR day-of-week rule and daylight-saving weeks. Explain a 5-field cron expression and list when it will next run. Send the expression (minute hour day-of-month month day-of-week, or @daily, @hourly and the other nicknames), the IANA time zone the cron daemon itself runs in (its TZ or system zone, e.g. America/Chicago; default UTC), a start date and time in that zone, and how many runs you want (1 to 50, default 10). Get back each field's values in plain words, whether the day-of-month OR day-of-week rule applies, and the next run times after the start, each with its local time, UTC offset and UTC instant. Runs that fall in a daylight-saving gap or in a repeated hour are said plainly, with what cronie does there. It is one of the developer department tools LLPRO builds for the work agents do across business software (GitHub, Aws, Kubernetes, Linux). Every answer carries the written rule it used, what it does not do, its sources with dates, and an Ed25519 signature you can check against the key below.
- Who it is for
- Agents and developers that write, review or debug scheduled jobs and need to know exactly when a cron line will run, including the day-of-month OR day-of-week rule and daylight-saving weeks.
- Price
- Free, no sign-up: 120 calls an hour per address and 3,000 an hour across all callers. Paid calls are planned and not charging.
- Limits
- Up to 30,000 bytes per call; larger requests are refused, never cut. Unknown fields are refused with the list of accepted ones. Nothing you send is stored by the tool; no model and no network are used. Does not read 6- or 7-field forms (seconds or year fields: Quartz, Spring, AWS EventBridge) or the extensions L, W, #, ? and H; does not do cronie's random '~' ranges. Other schedulers differ: systemd timers, Kubernetes CronJob and GitHub Actions (UTC only, may start late) have their own daylight-saving and delay rules; BusyBox and some BSD crons handle clock changes differently. Does not run or install anything, read a crontab file, its environment lines or its commands. Does not know future clock-change laws a government has not yet put into the IANA database (the database version is in every answer). Models the daemon's own zone only: with CRON_TZ in a crontab, cronie checks each real minute in the job's zone, so a run in a skipped time is missed and a run in a repeated time can happen twice; this tool does not model that. Not legal advice.
For developers: try it
POST https://llpro.ai/mcp
{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "cron_next_runs", "arguments": {"expression": "30 9 * * 1-5", "time_zone": "America/Chicago", "start_date": "2026-11-19", "start_time": "10:00", "count": 3}}}For agents
Tool cron_next_runs on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:4ixwacnuahqsgbra5p3f4rjtmi): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).
Public key (base64): ayb8B82dxamXv1hWF70LsMCNIit3l9lb8SR2BJeK6Wo=
For agents that search MCP registries for cron expression, crontab next run, cron schedule tools (listed in MCP registries, served by the Campus gateway: MCP, agent-to-agent and REST). One fixed, written rule per call, a signed record, no account needed.
Next
- Connect your agent: Use this and the other LLPRO tools from your own agent.
- Get your agent: No agent yet? Get one that asks first.
- Hand the whole job to the Hub: Reading a cron line is one step of scheduling a job. Tell the Hub the whole job; it routes you to the right signed tools (time zone converter, recurring dates).
For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card