Systems Manager

Sm Cron Operations

sm_cron_operations

Lists and removes cron jobs for a specified user, helping AI agents inspect and clean up scheduled tasks on managed hosts.

Instructions

Operations for cron jobs

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": {
      "action": "<action>"
    },
    "name": "sm_cron_operations"
  }
}

Input Schema

Name	Required	Description
`user`	No	User for cron job
`action`	Yes	Action to perform. Must be one of: 'list_cron_jobs', 'remove_cron_job'
`confirm`	No	Explicit confirmation for a mutating action. Pass true when the client cannot answer an approval prompt.
`job_ref`	No	Opaque job reference returned by list_cron_jobs

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.2.9Nov 3, 2026

addedInput schema / properties / confirm

Added value: +{
+  "default": false,
+  "description": "Explicit confirmation for a mutating action. Pass true when the client cannot answer an approval prompt.",
+  "type": "boolean"
+}

First observedv2.2.5Oct 24, 2026

TDQS

C2.2/5.0

Behavior2/5

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

With no annotations provided, the description carries the full behavioral burden and discloses nothing: not that 'remove_cron_job' is destructive and irreversible, not that 'confirm' exists for clients that cannot answer approval prompts, and not what permissions are needed. The word "Operations" hints at mutation but gives no safety context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The three-word description is brief but that brevity comes from under-specification, not efficiency. There is no front-loaded statement of what the tool does or which actions it supports.

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

Completeness2/5

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

For a tool containing a destructive remove action with zero annotations and no output schema, the description should explain action semantics, confirmation behavior, and the list-then-remove workflow. The schema covers the parameters well, but the description leaves the agent without the operational context needed to invoke this safely.

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 description coverage is 100%, so the baseline of 3 applies: parameters like job_ref ("opaque job reference returned by list_cron_jobs") and confirm are already well documented in the schema. The description adds nothing beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Operations for cron jobs" essentially restates the title "Sm Cron Operations" without naming a verb or scope. It does not distinguish this tool from siblings such as sm_system_operations, sm_process_operations, or sm_service_operations, which also end in "operations."

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 guidance on when to choose this tool over its many siblings, nor on prerequisites such as needing a job_ref from a prior list before removal. The action values exist only in the schema, not the description.

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