Skip to main content
Glama

cron

Read-only

Explain 5/6-field scheduling expressions, names, and @daily shortcuts, then list upcoming runs in a chosen timezone with daylight saving awareness.

Instructions

Explain a cron expression (5/6 fields, names, @daily) and list next runs in a zone, DST-aware.

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
countNodefault 10
startNo
timezoneNo
expressionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds useful behavioral context beyond that: DST-aware computation in a zone and that it returns both an explanation and the next runs; it doesn't mention limits on count or how start interacts with evaluation.

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 tightly packed sentence with the core action, accepted input formats, zone/DST qualifier, and output content front-loaded. Nothing is redundant.

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 read-only utility with four simple parameters and no output schema, the description covers the essentials: input formats, timezone semantics, and what is returned. Minor gaps around count defaults/limits and start semantics prevent a 5.

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 only 25%, and the description compensates by clarifying the expression formats accepted (5/6 fields, names, @daily) and the timezone's DST handling. The count and start parameters remain unexplained in both schema and description, keeping it below 5.

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 states a specific verb and resource: explain a cron expression and list its next runs, noting accepted formats (5/6 fields, names, @daily) and DST-aware zone handling. It is distinguishable from siblings like date_add or calendar, though it doesn't name an alternative for scheduling-style queries.

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 implied by the description—use it to interpret a cron string and preview upcoming fire times—but there is no explicit when-to-use/when-not-to-use guidance and no named alternative for adjacent date/time tools.

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