Skip to main content
Glama
AgenSysAdmin

AgenSysAdmin

by E13ctr0N

check_cron

Read-only

Lists user crontab and system /etc/cron.d/ cron jobs on a remote Linux server, helping you inspect scheduled tasks before troubleshooting or changing them.

Instructions

List cron jobs — user crontab and system /etc/cron.d/ entries.

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": {
      "server": "<server>"
    },
    "name": "check_cron"
  }
}

Input Schema

NameRequiredDescriptionDefault
userNo
serverYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful scope context — it will surface both user crontab and system /etc/cron.d/ entries — but omits whether /etc/cron.d/ requires elevated permissions, whether other cron locations (/etc/crontab, cron.hourly/daily) are included, and what the returned entries look like.

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?

A single short sentence that is front-loaded with the verb and resource, with the scope detail appended after the dash. No filler, though it is so terse that the scope clause is doing work the rest of the definition should also do.

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?

For a simple read-only inspection tool this is minimally adequate: safety is covered by annotations and there is no output schema to explain. However, with 0% schema coverage and no output schema, the definition leaves both the 'user' parameter and the shape of the returned cron entries undocumented.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning and largely fails to. The optional 'user' parameter is never explained — it is unclear whether it selects whose crontab is read or filters results, nor what null does; only the 'server' parameter is loosely implied by context.

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?

Names a specific verb and resource ("List cron jobs") and scopes it to two concrete sources: the user crontab and /etc/cron.d/ entries. It is distinguishable from siblings like check_services or process_list by resource, though it never explicitly contrasts itself with them.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisite notes, and no mention of when another tool would be preferable. The agent must infer that this is for inspecting scheduled tasks, and must also infer whether root/elevated access is needed for the /etc/cron.d/ portion.

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