Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

linux_systemd_unit_generator

Read-onlyIdempotent

Generate a complete systemd unit file by providing structured section fields for service, timer, socket, mount, path, or target types. Returns INI text and install commands without writing to disk.

Instructions

Systemd Unit Generator. Generate a complete systemd unit file from structured section fields and return the INI-style text ([Unit], the type body, [Install]) plus the install path and companion files. Set "operation" to "generate" (default) to build a unit, or "presets" to fetch ready-made example inputs. "unitType" selects the body section: service (ExecStart, Type, User, Restart, Environment, sandboxing), timer (OnCalendar/OnBootSec triggers, Persistent), socket (Listen* + Accept), mount (What/Where/Type/Options), path (Path* watches), or target. Per-section directives go in the matching object (unit, service, timer, socket, mount, path, install); every emitted directive is validated and missing ExecStart/triggers or weak hardening produce a warnings list (the unit is still returned). It only BUILDS the file text and copy-paste install commands — it never writes to disk, runs systemctl, enables, or starts any unit, and needs no privileges. Use this to author a .service/.timer/.socket file; use linux_ssh_con

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationNo"generate" builds a unit from the fields below; "presets" ignores them and returns example inputs.generate
unitTypeNoRequired for generate. Selects which body section is emitted and the file extension. Case-insensitive.
filenameNoOutput unit filename. Defaults to the slugified description plus the unitType extension (e.g. my-unit.service).
descriptionNoHuman-readable unit summary; emitted as Description= in [Unit].
unitNo[Unit] directives keyed by directive name. Supports After, Before, Requires, Wants, Requisite, BindsTo, PartOf, Conflicts, OnFailure, Documentation, DefaultDependencies.
serviceNo[Service] directives (unitType=service). Common keys: Type, ExecStart (absolute path), Restart, RestartSec, User, Group, WorkingDirectory, Environment, plus sandboxing (PrivateTmp, ProtectSystem, ProtectHome, NoNewPrivileges) and limits.
timerNo[Timer] directives (unitType=timer). Keys: OnCalendar, OnBootSec, OnStartupSec, OnUnitActiveSec, OnUnitInactiveSec, OnActiveSec, AccuracySec, RandomizedDelaySec, Persistent, WakeSystem, RemainAfterElapse, Unit.
socketNo[Socket] directives (unitType=socket). Keys: ListenStream, ListenDatagram and other Listen* directives, Accept, SocketUser, SocketGroup, SocketMode, ReusePort, NoDelay, FileDescriptorName, MaxConnections.
mountNo[Mount] directives (unitType=mount). Keys: What (source, required), Where (absolute mount point, required), Type, Options, SloppyOptions, LazyUnmount, ForceUnmount, DirectoryMode, TimeoutSec.
pathNo[Path] directives (unitType=path). Keys: PathExists, PathExistsGlob, PathChanged, PathModified, DirectoryNotEmpty, MakeDirectory, Unit (unit to activate on trigger).
installNo[Install] directives. Keys: WantedBy (e.g. multi-user.target), RequiredBy, Alias, Also, DefaultInstance. Omitting it warns the unit cannot be enabled.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoAlways true on a 200 response.
operationNoEchoes the requested operation (generate or presets).
resultNoFor generate, the fields below. For presets, an object with a "presets" array of example requests.
Behavior5/5

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

Adds key behavioral details beyond annotations: validation, warnings, no disk writes, no privileges. Aligns perfectly with readOnlyHint and idempotentHint.

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?

Front-loaded with purpose but contains redundant enumeration of unit types across multiple sentences. Could be more concise; the cut-off also suggests it's overly long.

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?

Covers all essential aspects: operations, unit types, warning behavior, and non-destructive nature. Output schema exists, so return format isn't needed. Completeness is high despite minor redundancy.

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?

Schema covers 100% with descriptions. The tool description adds context about validation and warnings, and maps sections to objects, providing extra value beyond schema.

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 description clearly states it generates systemd unit files from structured fields. It distinguishes from siblings like linux_ssh_config_generator, though the sibling list is broad. The cut-off at the end slightly reduces clarity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Describes two operations (generate/presets) and emphasizes it never writes to disk or runs systemctl, guiding safe usage. However, it doesn't fully articulate when to use alternatives beyond the truncated mention of linux_ssh_con.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jambozx/onlinecybertools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server