CronSpell

List cron runs between two times

cron_runs_between

Read-onlyIdempotent

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.

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>",
      "start": "<start>",
      "end": "<end>"
    },
    "name": "cron_runs_between"
  }
}

Input Schema

Name	Required	Description	Default
`end`	Yes	Window 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.
`limit`	No	Max runs to return (1-100).
`start`	Yes	Window 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.
`timezone`	No	IANA time zone the schedule runs in, e.g. "America/Denver", "Europe/London". Default UTC.	UTC
`expression`	Yes	Cron expression, e.g. "0 9 * * 1-5", "/15 * * ", "0 30 8 * *" (6 fields = leading seconds) or "@daily".

Output Schema

Name	Required	Description	Default
`end`	No
`runs`	Yes
`notes`	Yes
`start`	No
`version`	Yes
`complete`	No
`timezone`	Yes
`truncated`	Yes
`expression`	Yes
`normalized`	No
`description`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description still adds genuinely new behavior: DST-aware evaluation, oldest-first ordering, default 20 / max 100 limit, and a truncated flag when results exceed the cap. 'Read-only' and the endpoint-engine reference restate structured or irrelevant information rather than adding value.

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?

Effectively two sentences plus a clause, front-loaded with the core action and window semantics before pagination details. Every fragment earns its place; nothing redundant beyond the already-annotated 'Read-only.'

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?

For a read-only listing tool with full schema coverage, complete annotations, and an output schema, the description covers everything an agent needs: window semantics, time zone handling, ordering, and the truncation signal. Return-value shape is correctly left to the output schema.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning on top: both endpoints are inclusive, the time zone governs schedule interpretation and is DST-aware, and limit defaults to 20 with a 100 cap. It stops short of 5 only because the accepted time formats are left entirely to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource (list every run of a cron expression) with scope nailed down: bounded between start and end, inclusive, in an IANA zone. The bounded-window framing implicitly separates it from next_cron_runs, but no sibling is named explicitly, so it stops short of 5.

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?

'between start and end (both inclusive)' gives an agent a clear selecting condition: use this when you have both endpoints, versus forward-looking or explanatory siblings. No explicit when-not or named alternative is given, which keeps it from 5.

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

All CronSpell tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?