Validate a schedule
cron_validate_scheduleValidate a cron expression before saving a job and get valid true/false, exact engine error, plain-English description, normalized form, warnings, and first scheduled run.
Instructions
Check a cron expression before saving it as a job: valid true/false with the engine's exact error (including wrong-field hints for Quartz-style forms), the plain-English description, the normalized form, advisory warnings, and the first scheduled run, all from the server's scheduling engine. The dialect includes L (last day), L-n (n days before it), nW / LW (nearest / last weekday) and Ln / d#n (last / nth weekday: L5 = last Friday, 5#3 = third Friday). Use it before saving a new or changed schedule; use cron_explain_schedule to list more upcoming runs, or cron_why_no_run for a job that already exists.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"expression": "<expression>"
},
"name": "cron_validate_schedule"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tz | No | IANA time zone the job will run in. It turns on the daylight saving time checks. | |
| seed | No | Name of the job that will use the expression, which resolves Jenkins-style H fields to that job's slot. For a workflow's schedule, use dag:<name>. Required when the expression uses H. | |
| expression | Yes | Cron expression, such as 0 3 * * 1-5. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| lint | No | ||
| seed | No | ||
| error | No | ||
| fires | No | ||
| valid | Yes | ||
| reboot | No | ||
| resolved | No | ||
| timezone | Yes | ||
| expression | Yes | ||
| normalized | No | ||
| description | No | ||
| never_fires | No |