Skip to main content
Glama

parse_cron

Parse cron expressions to get next scheduled execution times and a plain-English description. Helps validate jobs, explain schedules, and debug scheduler configuration.

Instructions

Parse a cron expression and return next execution times with a human description.

Accepts standard 5-field cron syntax (minute hour day month weekday) and
the extended 6-field format (with seconds prefix). Returns the next several
scheduled times and a plain-English description of the schedule. Useful for
validating cron jobs, explaining schedules to non-technical stakeholders, or
debugging scheduler configuration.

Args:
    expression: Cron expression to parse. Supports:
        5-field: '0 9 * * 1' (every Monday at 09:00)
        6-field: '0 0 9 * * 1' (with leading seconds field)
        Special strings: '@daily', '@weekly', '@monthly', '@hourly'
        Ranges: '0 9-17 * * 1-5' (hourly 9am-5pm on weekdays)
        Step values: '*/15 * * * *' (every 15 minutes)

Returns:
    description: Plain-English schedule description.
    next_runs: List of the next 5 scheduled UTC datetime strings.
    fields: Parsed cron fields with each component's meaning.
    timezone: Assumes UTC unless a POSIX TZ string is prepended.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
expressionYes
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses that it assumes UTC unless a POSIX TZ string is prepended, returns 5 next runs, and lists returned fields. It implies a read-only, stateless operation, which is appropriately transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with an overview, an 'Args' section, and a 'Returns' section. It is detailed yet concise, with every sentence adding value and no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given one parameter and no output schema, the description thoroughly documents input options and briefly describes output fields (description, next_runs, fields, timezone). It could provide more details on output format (e.g., datetime string format), but is largely complete for agent use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

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

The single parameter 'expression' has 0% schema description coverage. The description compensates fully with detailed examples: 5-field, 6-field, special strings, ranges, step values. This provides extensive meaning beyond the schema's bare type definition.

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 clearly states it parses cron expressions and returns next execution times with a human description. It specifies supported formats (5-field, 6-field, special strings, ranges, step values), distinguishing it from sibling tools that handle validation, DNS, SSL, etc.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states use cases: validating cron jobs, explaining schedules, debugging scheduler configuration. While it doesn't list exclusions, the sibling tools are unrelated, so usage context is sufficient.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ForeverTools/kiprio-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server