Skip to main content
Glama
Systems Manager

Systems Manager

List Cron Jobs

sm_cron_list_cron_jobs
Read-onlyIdempotent

Lists scheduled cron jobs on a system, optionally filtered by user, to help inspect and manage recurring tasks.

Instructions

List cron jobs (sm_cron_operations). Operations for cron jobs

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sm_cron_list_cron_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
userNoUser for cron job

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.11

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered. The description contributes nothing beyond that — no mention of what is returned, whether the list is host-wide, or how the optional user filter changes results.

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

Conciseness3/5

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

It is short and front-loaded with the verb and resource, which is good. However, the second sentence 'Operations for cron jobs' is pure filler that earns no place and dilutes the signal.

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 list tool with one optional, fully documented parameter and complete annotations, the definition is minimally sufficient. It still omits what a cron job entry contains and whether the optional user argument narrows or is required for meaningful results.

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% and the single optional 'user' parameter is documented in the schema as 'User for cron job'. The description adds no extra meaning about whether this filters to one user's crontab or defaults to all users, so the baseline 3 applies.

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?

The first sentence pairs a specific verb (List) with a specific resource (cron jobs), which is enough for an agent to distinguish it from sm_cron_remove_cron_job. The trailing phrase 'Operations for cron jobs' is a vague restatement that adds no further precision.

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 explicit when-to-use guidance and no mention of alternatives or prerequisites. The verb 'List' implies a read-only enumeration, but the agent is left to infer that on its own.

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

Deploy Server

Other Tools