Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

linux_cron

Read-onlyIdempotent

Compose a crontab schedule line from minute, hour, day-of-month, month, and day-of-week inputs, outputting the expression with a plain-English explanation and common examples.

Instructions

Cron Job Schedule and Crontab Line Generator. Build a 5-field crontab schedule from individual minute/hour/day-of-month/month/day-of-week inputs and assemble the ready-to-paste crontab line " ", plus a plain-English explanation of each field and a curated list of common schedule examples. It only BUILDS the schedule text — it never installs a cron job, edits crontab, or touches the system. Use this to compose or teach a schedule from parts; use time_cron_parser instead when you already HAVE a cron expression and want to decode it to English or preview real next-run times (this tool's nextRuns is a placeholder note, not computed times). Runs locally via a Node bridge: read-only, non-destructive, idempotent, offline, contacts no external service, and is rate-limited (anonymous 30/min, 200/hr, 1000/day).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
minuteNoMinute field (0-59). Accepts *, lists (0,30), ranges (0-29), steps (*/5).*
hourNoHour field (0-23). Accepts *, lists, ranges, steps (*/6).*
dayOfMonthNoDay-of-month field (1-31). Accepts *, lists, ranges, steps.*
monthNoMonth field (1-12). Accepts *, lists, ranges; numbers are named in the explanation.*
dayOfWeekNoDay-of-week field (0-6, 0=Sunday). Accepts *, lists, ranges; numbers are named in the explanation.*
commandNoCommand appended verbatim after the expression to form the crontab line; not validated or executed./path/to/script.sh
generateExamplesNoWhen true, includes the curated examples array of common cron schedules.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoAlways true on a 200 response.
cronLineNoFull crontab line: the 5-field expression followed by the command.
expressionNoThe assembled 5-field cron expression, e.g. "*/5 * * * *".
commandNoThe command echoed back as used in cronLine.
explanationNoPlain-English breakdown of each field plus a combined summary sentence.
nextRunsNoPlaceholder only — contains a note and the expression; actual next-run times are NOT computed (use time_cron_parser for real firing times).
examplesNoPresent when generateExamples is not false. Common cron schedules.
errorNoPresent instead of the result fields when generation fails (HTTP 400).
Behavior5/5

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

Description adds full behavioral detail: local, read-only, non-destructive, idempotent, offline, rate limits. Annotations already cover readOnly, destructive, idempotent; description enriches and does not contradict.

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?

Thorough but not overly long; front-loaded with purpose and output. Each sentence is informative. Minor redundancy with annotations but acceptable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Complete given 7 params and output schema. Covers purpose, usage, behavior, parameter details, and clarifies placeholder nextRuns. No gaps for a generation tool.

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 100% so baseline 3. Description adds context about generateExamples and notes that nextRuns is placeholder, plus that command is not validated. Adds some value beyond schema.

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?

Clearly states it's a schedule generator, builds crontab line, distinguishes from time_cron_parser. Specific verb 'build' and resource 'schedule' + 'line'.

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

Usage Guidelines5/5

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

Explicit when-to-use (compose/teach) and when-not (use time_cron_parser for decoding). States it never installs or edits crontab.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jambozx/onlinecybertools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server