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

io.github.crunchtools/systemd

by crunchtools

Daemon Reload Tool

daemon_reload_tool

Reload systemd's unit file cache after creating or modifying unit files so systemd recognizes the changes without restarting the system.

Instructions

Reload systemd's unit file cache (equivalent to systemctl daemon-reload).

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": "daemon_reload_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.6/5.0
Behavior3/5

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

With no annotations the description carries the full burden. "Reload's unit file cache" correctly signals a system-wide, non-destructive manager refresh rather than a service restart, which is genuinely useful, but it omits privilege requirements (root), failure modes, and whether running units are affected.

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?

A single sentence, front-loaded with the effect and followed by the canonical equivalent. No filler, no restatement of the tool name.

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?

The output schema exists, so return values need no explanation, and zero parameters keeps the surface small. Still, for a system-wide mutation with no annotations, the agent is left without guidance on prerequisites or sequencing relative to unit_file_write_tool.

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; baseline 4 applies. The description correctly implies a parameterless call by framing the action as a global manager operation.

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 ("Reload systemd's unit file cache") and anchors it to the well-known systemctl equivalent, so the operation is unambiguous. It does not, however, distinguish itself from the adjacent unit_reload_tool, which is the most likely sibling confusion (per-unit config reload vs. manager cache reload).

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?

No explicit when-to-use or when-not-to-use statement. The systemctl equivalency lets a systemd-knowledgeable agent infer the typical trigger (after writing or removing unit files), but the description never says so, nor does it point at unit_file_write_tool / unit_file_remove_tool as the preceding steps.

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