Skip to main content
Glama

CronSpell

by dev.workers.mike-tusa.cronspell
OverviewDiscussionsAdmin

Server Details

Validate and explain cron expressions; list next/previous run times in any time zone, DST-aware.

Ownership verified
Status
Healthy
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL

TDQS

Score is being calculated.

Available Tools

4 tools
cron_runs_betweenList cron runs between two times
Read-onlyIdempotent
Inspect

List every run of a cron expression between start and end (both inclusive) in an IANA time zone, DST-aware, oldest first. Default limit 20, max 100; truncated is true when there are more. Read-only. Same engine as GET /api/between.

ParametersJSON Schema
NameRequiredDescriptionDefault
endYesWindow end (inclusive). ISO 8601 with Z or an offset (2026-11-01T09:00:00Z), a local time read in the time zone (2026-11-01T09:00), or unix seconds.
limitNoMax runs to return (1-100).
startYesWindow start (inclusive). ISO 8601 with Z or an offset (2026-11-01T09:00:00Z), a local time read in the time zone (2026-11-01T09:00), or unix seconds.
timezoneNoIANA time zone the schedule runs in, e.g. "America/Denver", "Europe/London". Default UTC.UTC
expressionYesCron expression, e.g. "0 9 * * 1-5", "*/15 * * * *", "0 30 8 * * *" (6 fields = leading seconds) or "@daily".

Output Schema

ParametersJSON Schema
NameRequiredDescription
endNo
runsYes
notesYes
startNo
versionYes
completeNo
timezoneYes
truncatedYes
expressionYes
normalizedNo
descriptionNo
explain_cronExplain a cron expression
Read-onlyIdempotent
Inspect

Explain a cron expression in plain English, e.g. "0 9 * * 1-5" → "At 09:00, on Monday through Friday." Also returns notes on cron rules that often surprise people (day-of-month OR day-of-week, seconds field, shorthand expansion). Invalid expressions return isError with the reason. Read-only. Same engine as GET /api/explain.

ParametersJSON Schema
NameRequiredDescriptionDefault
expressionYesCron expression, e.g. "0 9 * * 1-5", "*/15 * * * *", "0 30 8 * * *" (6 fields = leading seconds) or "@daily".

Output Schema

ParametersJSON Schema
NameRequiredDescription
notesNo
formatNo
versionYes
expressionYes
normalizedNo
dayMatchingNo
descriptionYes
next_cron_runsList next (or previous) cron run times
Read-onlyIdempotent
Inspect

List the next (or, with direction "previous", the most recent past) run times of a cron expression in an IANA time zone, DST-aware. Each run has the local time with its UTC offset, the UTC time, unix seconds and weekday. Default 5 runs, max 20; searches up to 50 years. Read-only. Same engine as GET /api/next and GET /api/previous.

ParametersJSON Schema
NameRequiredDescriptionDefault
fromNoStart point (exclusive); default now. ISO 8601 with Z or an offset (2026-11-01T09:00:00Z), a local time read in the time zone (2026-11-01T09:00), or unix seconds.
countNoHow many runs (1-20).
timezoneNoIANA time zone the schedule runs in, e.g. "America/Denver", "Europe/London". Default UTC.UTC
directionNo"next" (default) or "previous" (most recent first).next
expressionYesCron expression, e.g. "0 9 * * 1-5", "*/15 * * * *", "0 30 8 * * *" (6 fields = leading seconds) or "@daily".

Output Schema

ParametersJSON Schema
NameRequiredDescription
fromNo
runsYes
notesYes
versionYes
completeYes
timezoneYes
directionNo
expressionYes
normalizedNo
descriptionNo
validate_cronValidate a cron expression
Read-onlyIdempotent
Inspect

Check whether a cron expression is valid. Returns valid true with the expanded values of every field (minute, hour, day of month, month, day of week, and seconds for 6-field expressions), or valid false with an error code, the field at fault and a message. Detects schedules that can never run (e.g. February 30). Read-only. Same engine as GET /api/validate.

ParametersJSON Schema
NameRequiredDescriptionDefault
expressionYesCron expression, e.g. "0 9 * * 1-5", "*/15 * * * *", "0 30 8 * * *" (6 fields = leading seconds) or "@daily".

Output Schema

ParametersJSON Schema
NameRequiredDescription
errorNo
validYes
fieldsNo
formatNo
versionYes
expressionYes
normalizedNo
dayMatchingNo
descriptionNo

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 4 tool updates
    • First observedcron_runs_between
    • First observedexplain_cron
    • First observednext_cron_runs
    • First observedvalidate_cron

Related MCP Connectors

Related MCP Servers

  • cron-explainer

    IdoAzaCalls
    A
    license
    Not graded
    quality
    D
    maintenance
    Parses cron expressions, returns next fire times, and provides an English description.
    MIT

  • cron-check

    arhancanli
    A
    license
    A
    quality
    B
    maintenance
    Explains cron expressions in plain English, checks them for errors and gotchas, lists next run times in any time zone, and converts between Unix cron, GitHub Actions, Kubernetes, AWS EventBridge, Quartz and Spring dialects.
    3
    1
    MIT

  • cron-schedule-audit-mcp

    tylerscomic-lab
    A
    license
    Not graded
    quality
    D
    maintenance
    Validates cron expressions and computes DST-correct next-fire times against real IANA timezone data, flagging schedules that silently skip a spring-forward run or double-fire on fall-back. Also surfaces the POSIX day-of-month/day-of-week OR semantics and other semantic footguns before a job ships.
    MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources