Skip to main content
Glama
gjenkins20

webmin-mcp-server

create_cron_job

Create a scheduled cron job by specifying a command and cron schedule (minutes, hours, days, months, weekdays). Supports wildcards and step values like */5.

Instructions

Create a new scheduled cron job. Specify the command to run and the schedule using cron syntax (minutes, hours, days, months, weekdays). Use '' for 'every' (e.g., '/5' for every 5 minutes).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serverNoServer alias (e.g., 'pi1', 'web-server'). Uses default server if not specified.
commandYesCommand to execute
minutesNoMinutes (0-59, or * for every minute, or */5 for every 5 minutes)*
hoursNoHours (0-23, or * for every hour)*
daysNoDay of month (1-31, or * for every day)*
monthsNoMonth (1-12, or * for every month)*
weekdaysNoDay of week (0-7, 0 and 7 are Sunday, or * for every day)*
userNoUser to run the job asroot
activeNoWhether the job is active
Behavior2/5

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

No annotations provided; description lacks disclosure of behavioral traits such as required permissions, overwrite behavior, or side effects on the system.

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?

Two sentences that are efficient and to the point, with no redundant or verbose language.

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

Completeness3/5

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

No output schema; description does not mention return values or side effects of creating a cron job, leaving some context gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so description adds limited value beyond schema. It provides cron syntax examples but does not significantly enhance parameter understanding.

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?

Description clearly states 'Create a new scheduled cron job' with verb and resource, and distinguishes from siblings like edit_cron_job and delete_cron_job.

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?

Description implies usage for creating new cron jobs but does not explicitly state when to use this tool versus alternatives like edit_cron_job.

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/gjenkins20/webmin-mcp-server'

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