Skip to main content
Glama

cron/manage

DestructiveIdempotent

Read or replace a user's crontab to manage scheduled commands, and list accounts that have one. Writes replace the whole file; other accounts require privileged access.

Instructions

Reads or replaces a user's crontab, the list of commands cron runs for that account on a schedule, and lists which accounts have one. Without content it reads: your own crontab as raw text exactly as crontab -l prints it (empty when you have none), or with privileged: true and no user, a table of the accounts that have a crontab and that your grant lets you view. With content it writes: the WHOLE crontab is replaced (an empty string clears it); the crontab command rejects a file it cannot parse and then the old crontab is unchanged; a missing final newline is added; the limit is 64 KiB. Your own crontab needs no grant and runs as you. Another account's needs privileged: true and a rule naming that account in your cron/manage grant (users: {name: {view: true, edit: true}}); edit implies view, root's crontab can be viewed but never edited, and cron.allow/cron.deny still apply to that account. WARNING: writing a crontab schedules commands as that user, and the job outlives this session and the revocation of your token; every write is audit-logged (size, lines, hash, never the content). To avoid overwriting a change made meanwhile, pass if_match with the sha256 you read (output_format: json returns it). For systemd timers use timers/list. Needs the crontab command on the host; inside a container a call sees the container's own crontabs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userNoAccount whose crontab to read or replace; default is your own. Another account needs privileged: true and a rule for it
contentNoThe complete new crontab; present = write (empty string clears it), absent = read. Standard crontab syntax: `m h dom mon dow command`, `@daily`, and NAME=value lines
if_matchNosha256 of the crontab as you read it; the write is refused if it has changed since
privilegedNoNeeded to list crontabs or to act on another account (needs a cron/manage grant); ignored for your own crontab
output_formatNo'json' (also yaml/table/wide, which return the same JSON) returns {user, exists, lines, jobs, bytes, sha256, content} for a read; default is the raw text

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.1

TDQS

A4.8/5.0
Behavior5/5

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

Far exceeds the annotations (destructiveHint/readOnlyHint/idempotentHint): discloses whole-crontab replacement, empty-string clearing, rejection of unparseable files leaving the old crontab intact, added final newline, 64 KiB limit, audit logging (size/lines/hash, never content), job persistence beyond session/token revocation, and container scoping. This is exactly the behavioral context annotations cannot carry.

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?

The core read/write distinction is front-loaded and every sentence is functional, but it is a dense single paragraph carrying a lot of interleaved detail (grants, edge cases, limits, warnings) that would benefit from tighter structuring.

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?

For a destructive read/write tool with no output schema, it covers permissions, concurrency, failure semantics, size limits, audit trails, and the container caveat. Nothing an agent needs to call it safely is missing.

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 baseline is 3, but the description adds real meaning: `content` presence triggers write vs read, `if_match` enables optimistic-concurrency protection, and `output_format: json` returns the sha256 needed for `if_match`. It also clarifies that `privileged` is ignored for your own crontab.

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 specific verbs and resource: 'Reads or replaces a user's crontab' plus the listing behavior. It explicitly distinguishes itself from the sibling timers/list ('For systemd timers use timers/list'), so an agent can route correctly without opening either schema.

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?

Gives explicit mode selection: without `content` it reads, with `content` it writes; spells out the `privileged`+`user` combinations, the grant rule requirement, and the alternative tool for systemd timers. When-to-use and prerequisites are fully covered.

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