Skip to main content
Glama

List next cron runs

list_cron_runs
Read-onlyIdempotent

Next run times of a 5-field cron expression (minute hour day month weekday) in any IANA timezone.

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

Input Schema

NameRequiredDescriptionDefault
afterNoStart from this ISO 8601 date-time (default now).
countNoNumber of runs (default 5).
timezoneNoIANA timezone name, e.g. Europe/Paris or America/New_York. Default UTC.
expressionYesCron expression, e.g. */15 9-17 * * mon-fri.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered. The description adds the useful constraint that input must be a 5-field expression, implicitly excluding seconds fields and shorthands like @daily, but says nothing about behavior on an invalid expression or how many results come back by default.

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 the format constraint up front and the timezone scope trailing. Every clause carries information and nothing is padded.

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?

For a pure-computation, non-mutating tool with full schema coverage and no output schema, the definition covers input format, expression shape, and timezone scope adequately. Error behavior on an unparseable cron expression is the only material gap, and it is minor.

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 would be 3, but the description adds real meaning by pinning the expression to exactly 5 fields in a stated order and confirming the timezone must be IANA. That constraint is not stated in the schema itself and prevents malformed 6-field or macro-style input.

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 the exact resource computed — next run times of a 5-field cron expression — with the field order spelled out, so an agent knows precisely what it returns. It omits an explicit verb (compute/list), but the purpose remains unambiguous and no sibling performs anything comparable.

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?

Usage is only implied: an agent infers it should call this when it needs upcoming cron fire times rather than actually scheduling anything. No when-not conditions, prerequisites, or alternatives are supplied, though within this catalog there is no comparable sibling to route away from.

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.