Skip to main content
Glama

Explain a schedule

cron_explain_schedule
Read-onlyIdempotent

Decode a cron expression into plain English, list upcoming run times in a time zone, and surface scheduling warnings so you can read or preview a schedule before using it.

Instructions

Decode a cron expression into a plain-English description, its next count run times as ISO timestamps in tz, and advisory warnings from the server's scheduling engine. Use it to read an expression or preview its runs; use cron_validate_schedule for the check before saving, or cron_why_no_run to test an existing job at a timestamp.

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_explain_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
tzNoIANA time zone to compute the runs in. Pass the job's zone. Defaults to UTC.
seedNoName 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.
countNoUpcoming runs to list.
expressionYesCron expression, such as 0 3 * * 1-5.

Output Schema

NameRequiredDescriptionDefault
lintNo
seedNo
errorNo
firesNo
validYes
rebootNo
resolvedNo
timezoneYes
expressionYes
normalizedNo
descriptionNo
never_firesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.2.73
    • addedInput schema / properties / count / default
      Added value: +5
    • addedInput schema / properties / count / description
      Added value: +"Upcoming runs to list."
    • addedInput schema / properties / count / maximum
      Added value: +60
    • addedInput schema / properties / count / minimum
      Added value: +1
    • addedInput schema / properties / expression / description
      Added value: +"Cron expression, such as 0 3 * * 1-5."
    • addedInput schema / properties / seed / description
      Added value: +"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."
    • addedInput schema / properties / tz / description
      Added value: +"IANA time zone to compute the runs in. Pass the job's zone. Defaults to UTC."
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description correctly spends its words elsewhere: it discloses that warnings come from the server's scheduling engine and that runs are returned in the caller-supplied zone. It doesn't note any H-field caveat in the prose (that lives only in the schema), which keeps it just short of a 5.

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?

Two sentences, front-loaded with the output shape followed by the routing guidance. No filler or restatement of the title.

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?

An output schema exists, so return values needn't be re-explained; the description covers purpose, output composition, and sibling routing. Combined with full schema coverage, an agent has everything needed to call it correctly.

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

Parameters3/5

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

Schema description coverage is 100% and the schema already documents tz defaults, count bounds, and the seed/H-field rule, so the baseline is 3. The description references `count` and `tz` but adds no syntax, format, or interaction detail beyond the schema.

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 ('Decode a cron expression') plus the full output payload: plain-English description, next `count` runs as ISO timestamps in `tz`, and scheduling-engine warnings. This is distinguishable at a glance from cron_validate_schedule or cron_why_no_run, which are named as alternatives.

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?

Explicitly routes the agent: use this to read an expression or preview runs, use cron_validate_schedule for the pre-save check, and cron_why_no_run to test an existing job at a timestamp. Both alternatives are named with the condition that selects them.

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