Skip to main content
Glama

Next runs of a cron expression

cron_next_runs
Read-onlyIdempotent

Next run times (UTC ISO) of a 5-field cron expression evaluated in a time zone (default UTC), plus the same times shown in another zone if given.

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

Input Schema

NameRequiredDescriptionDefault
countNo
show_inNoIANA zone to display times in, e.g. Asia/Seoul
timezoneNoIANA zone the cron is evaluated in, default UTC
expressionYes5-field cron or @daily/@hourly/@weekly/@monthly/@yearly

Output Schema

NameRequiredDescriptionDefault
runsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: results are returned as UTC ISO strings and can also be rendered in a second zone, which tells the agent what the output looks like in substance. It does not mention the maximum count or behavior on an invalid expression.

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?

A single front-loaded sentence with no filler: the operation, output format, evaluation zone, and optional secondary zone all appear in order of importance. Nothing could be removed without losing information.

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?

With an output schema present and annotations covering safety, the description is nearly complete for a 4-parameter read-only utility. The one meaningful gap is that it says '5-field cron expression' while the schema also accepts @daily/@hourly/@weekly/@monthly/@yearly macros, which the description does not acknowledge.

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 coverage is 75%, so timezone, show_in, and expression are already documented in the schema; the description mostly restates the timezone default. It does clarify that show_in means displaying the same instants in another zone, which is more than the schema's 'zone to display times in', but it never mentions the count parameter or its 1–20 bound.

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?

The description names a specific operation and resource: computing the next run times of a 5-field cron expression, with the evaluation time zone and output format stated. It is unambiguous about what the tool returns, though there are no sibling tools to distinguish it from.

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

Usage Guidelines3/5

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

There is no explicit when-to-use or when-not-to-use guidance, but the purpose statement makes the use case self-evident for a cron-scheduling utility. It adds the useful default (UTC) and the optional secondary-zone display, which implicitly tells the agent what show_in is for.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources