Reload a systemd service's configuration without restarting it to apply changes with minimal disruption. Provide the unit name; optionally choose a configured host.
Reload a systemd service's configuration without restarting it.
| Name | Required | Description | Default |
|---|---|---|---|
| host | No | target host name from the opsgate config; omit for the default host | |
| name | Yes | systemd unit name, for example nginx or docker.service |
Changes observed during successful MCP inspections.
v0.1.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It does disclose the key behavioral trait — the service is not restarted, so the reload is non-disruptive — but says nothing about required privileges (systemd/root access), whether the unit must be running, or what happens on reload failure.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence with the scope and the critical non-restart distinction front-loaded. No filler, nothing that fails to earn its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Parameters are fully covered by the schema and no output schema exists, so little is required. However, for an unannotated mutation tool, the absence of permission requirements and failure semantics leaves a meaningful gap for an agent deciding whether it can safely call it.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%: 'name' and 'host' are both fully documented in the schema, including the opsgate-config sourcing of host. The description adds no syntax or format detail beyond that, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Specific verb (reload) plus resource (systemd service configuration) with the key differentiator from the closest sibling stated explicitly: 'without restarting it' contrasts directly with service_restart. It does not clarify its relationship to nginx_reload, a specialized variant, but the core purpose is unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The 'without restarting' phrasing implies when to prefer this over service_restart (avoiding downtime), but the description never states a when-to-use rule or names the alternative tool. Usage is inferable rather than guided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.