Epoch Calculator

cron_next_runs

Read-only

Explain a 5- or 6-field cron expression in plain English and list its next run times in a time zone (as ISO 8601 and Unix timestamps). Use to answer "when does this cron job run next?" or to validate an expression.

Input Schema

TableJSON Schema

Name	Required	Description
`from`	No	Start evaluating after this date/time (ISO 8601). Defaults to now.
`count`	No	How many upcoming runs to return. Default 5.
`timezone`	No	Zone the schedule is evaluated in. Defaults to UTC.
`expression`	Yes	Cron expression, e.g. "0 9 * * 1-5".

Output Schema

TableJSON Schema

Name	Required	Description
`timezone`	Yes
`next_runs`	Yes
`expression`	Yes
`description`	Yes	Plain-English reading of the expression.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedSep 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "description": {
+      "description": "Plain-English reading of the expression.",
+      "type": "string"
+    },
+    "expression": {
+      "type": "string"
+    },
+    "next_runs": {
+      "items": {
+        "properties": {
+          "epoch_seconds": {
+            "type": "integer"
+          },
+          "iso": {
+            "type": "string"
+          },
+          "utc_iso": {
+            "type": "string"
+          },
+          "weekday": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "iso",
+          "utc_iso",
+          "epoch_seconds",
+          "weekday"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "timezone": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "expression",
+    "description",
+    "timezone",
+    "next_runs"
+  ],
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and non-destructive behavior, and the description adds observable behavior: plain-English explanation plus output in both ISO 8601 and Unix timestamps. It does not mention the dynamic 'from' default, but the schema covers defaults and annotations cover safety.

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 focused sentences with no filler: the first states the core function and output format, the second gives concrete use cases. Information is front-loaded and every clause earns its place.

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?

The description is complete for this tool: it explains the purpose, output format, and use cases, while parameters and return structure are covered by a 100% schema-described input and a dedicated output schema. Annotations also cover the safety profile, so no critical context is missing.

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 description coverage is 100%, so the baseline is 3. The description adds extra meaning by specifying '5- or 6-field' cron expressions, which clarifies the expected format beyond the schema's example. Other parameters are not elaborated, but the schema already documents them well.

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 uses a specific verb-resource pair: explain a 5- or 6-field cron expression and list its next run times. It clearly distinguishes this tool from the sibling date/time utilities, none of which handle cron expressions or next-run computation.

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 gives usage scenarios: answer 'when does this cron job run next?' or validate an expression. It does not explicitly contrast against alternatives, but the sibling tools are clearly different, making the intended context obvious.

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

All Epoch Calculator tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation5/5

Each tool targets a distinct date/time operation: conversion, timezone shifting, cron scheduling, duration, countdown, arithmetic, parsing, and current time. Even the inverse operations (convert_timestamp vs parse_datetime) are clearly separated by input/output direction.

Naming Consistency3/5

Names are uniformly snake_case and readable, but they mix verb_noun patterns (convert_timestamp, parse_datetime) with noun-phrase or query-style names (date_duration, time_now, days_until, epoch_math, cron_next_runs). This is consistent in style but not in grammatical pattern.

Tool Count5/5

Eight tools is well-scoped for a date/time and epoch calculator. Each tool covers a distinct facet of the domain without redundancy or bloat.

Completeness5/5

The tool surface covers the full lifecycle of date/time operations: current time, parsing, formatting, timezone conversion, arithmetic, duration, countdowns, and cron scheduling. No significant gaps that would block common use cases.

Resources

Need Help?