Skip to main content
Glama

devops-linux

docker_to_systemd

Translate docker run CLI commands or docker-compose.yml files into hardened Linux systemd .service or Podman Quadlet .container units.

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

Input Schema

NameRequiredDescriptionDefault
textNodocker run command or docker-compose.yml content.
filePathNo
rootlessNo
serviceNameNo
outputFormatNohardened

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden and falls short. It does not say whether units are written to disk or returned as text, which parameters are mutually exclusive (text vs filePath, and both are non-required), what 'hardened' actually adds, or whether any prerequisites/permissions are needed.

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 well-formed sentence that front-loads the verb and both input forms before naming the outputs. No filler or redundancy.

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 translation tool the core contract (sources to targets) is stated clearly and no output schema is needed. However, with five parameters, zero required fields, and no annotations, the definition should say more about filePath vs text and the meaning of 'hardened' / rootless to be fully actionable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 20% (only 'text' is documented), and the description only clarifies that 'text' accepts either a docker run command or compose content, plus loosely echoes the outputFormat values. filePath, rootless, and serviceName are unexplained in both schema and description, and the text/filePath relationship is left ambiguous.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb ('Translate') plus both source resources (docker run commands, docker-compose.yml) and both target artifacts (systemd .service, Podman Quadlet .container). An agent can immediately tell this is a Docker-to-systemd/Quadlet converter, distinct from the sibling systemd_security_audit.

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 input/output framing implies when the tool applies (you have a docker run string or compose file and want native units), but there is no explicit when-to-use, when-not-to-use, or named alternative. Nothing tells the agent which of the three output formats to pick or when rootless mode matters.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources