Skip to main content
Glama

Read a cron expression and list its next runs

cron
Read-only

Explains a cron expression in plain English and lists its next runs in UTC and in a time zone. Five fields (minute hour day month weekday), or six with seconds first. Names (MON, JAN) and steps are supported. Computed in the Worker; no network call. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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

Input Schema

NameRequiredDescriptionDefault
tzNoIANA time zone for the local times, e.g. Europe/Berlin (default UTC)
countNoNext runs, 1 to 20 (default 5)
expressionYesCron expression, 5 or 6 fields

Output Schema

NameRequiredDescriptionDefault
sourceNo
nextRunsNo
timezoneNo
checkedAtNo
expressionNo
explanationNo
nextRunsUtcNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Adds substantively beyond the annotations: it discloses the pricing model ($0.002 per successful call via x402 in USDC on Base/Solana), that failed calls are not charged, and that computation runs locally in the Worker. There is mild tension between 'no network call' and the openWorldHint=true annotation, but the payment settlement rails plausibly explain the open-world flag, so this reads as imprecision rather than contradiction.

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

Conciseness4/5

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

Front-loaded with the purpose, then format support, then execution/pricing traits. Every sentence carries information, though the pricing sentence is long and packs payment-network detail that could be trimmed without loss for most callers.

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?

An output schema exists, so return values need no explanation, and all three parameters are covered. Cost and payment mechanism are disclosed, which matters for a paid tool. The only omission is behavior on invalid expressions beyond the note that failed calls are not charged.

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 tz and count are already documented with defaults. The description still adds value by clarifying expression syntax support (field count, seconds-first variant, named months/weekdays, step values) and by reinforcing that times are returned in both UTC and a chosen zone, which the schema does not say.

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 and resource pair: it 'explains a cron expression in plain English and lists its next runs in UTC and in a time zone.' The scope (both a human-readable explanation and computed future runs) is unambiguous and no sibling tool in the catalog covers cron parsing, so no differentiation is needed.

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?

Gives clear invocation context: five fields (minute hour day month weekday) or six with seconds first, names like MON/JAN and steps supported. It does not state when to prefer it over anything else, but there is no comparable alternative among the siblings, so the absence of exclusions is not a real gap.

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