Skip to main content
Glama

TestingAPIs API tools

Explain a cron expression

explain_cron
Read-onlyIdempotent

Read a cron expression (5 fields as in crontab, GitHub Actions and Kubernetes, or 6 with seconds as in Spring/Quartz, or @daily and the other shortcuts) in plain English, and list its next run times in UTC.

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

Input Schema

NameRequiredDescriptionDefault
countNoHow many next run times to list (5 by default).
expressionYesThe cron expression, such as */15 * * * *.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds value by disclosing what the caller actually gets back — a plain-English explanation plus a list of upcoming runs in UTC — which matters since no output schema exists. It does not say what happens on an invalid expression, a minor remaining gap.

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?

One sentence, front-loaded with the core action and output, with the format variants packed into parentheticals. Dense but every clause carries information; only the closing UTC note could be tightened.

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 simple two-parameter read-only utility, the definition covers input dialects, output content, and timezone (UTC). The only omissions are error behavior for malformed expressions and whether count affects only the run-time list, neither of which blocks correct invocation.

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 both parameters are already documented in structured form. The description still adds meaning to the expression parameter by naming the concrete accepted formats (5-field, 6-field with seconds, @daily-style shortcuts), which the schema only hints at with a single example.

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 reads/explains a cron expression in plain English and returns the next run times. The scope is unambiguous and clearly distinct from the JSON/OpenAPI-oriented siblings in the catalog.

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 context for use by enumerating accepted input dialects (5-field crontab, 6-field Spring/Quartz, @shortcuts), which tells an agent when this tool applies. It stops short of explicit when-not guidance, but no sibling overlaps this function.

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