Skip to main content
Glama
io.github.crunchtools/systemd

io.github.crunchtools/systemd

by crunchtools

List Jobs Tool

list_jobs_tool
Read-only

Lists pending systemd jobs to reveal stuck starts, stops, and reloads, helping diagnose blocked unit lifecycle operations.

Instructions

List pending systemd jobs — reveals stuck starts/stops/reloads.

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": "list_jobs_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, and an output schema covers the return shape, so the bar is lower. The description contributes a small amount of extra context by framing the output around stuck/in-flight operations, but discloses nothing about scope (all pending jobs system-wide?) or cost.

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?

One short sentence, front-loaded with the verb and resource, with the diagnostic payoff delivered in the same clause. Nothing wasted.

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

Completeness4/5

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

For a 0-param, read-only tool with an output schema and a readOnlyHint, the description supplies the essential purpose and the practical reason to call it. It could be marginally stronger by noting scope or how jobs differ from unit state, but nothing critical 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a 0-param tool applies. Schema coverage is reported at 100%.

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?

States a specific verb and resource ("List pending systemd jobs") and adds a clarifying gloss that this surfaces stuck starts/stops/reloads. This is enough to distinguish it from unit_list_tool or failed_units_tool, though it never names those siblings explicitly.

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?

The phrase "reveals stuck starts/stops/reloads" implies the diagnostic scenario in which to reach for it, but there is no explicit when-to-use-vs-alternatives guidance, e.g. no pointer telling the agent to prefer unit_list_tool for a general inventory.

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