Skip to main content
Glama

devops-linux

systemd_security_audit

Audit a Linux systemd .service unit against 10 kernel sandboxing controls and compute its security exposure score (0.1 to 10.0).

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

Input Schema

NameRequiredDescriptionDefault
textNosystemd .service unit content.
filePathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/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. It does disclose real behavior beyond the schema (ten named control categories, a bounded 0.1–10.0 score), but it never states that the operation is read-only/non-mutating, whether the unit file is read from disk for filePath, or how the two input modes interact.

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 front-loaded sentence with the resource first and the scoring model second; nothing is redundant or padded.

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?

Against a two-parameter tool with no annotations and no output schema, the description compensates partially by explaining the scoring range, but it leaves open whether per-control findings are returned, which ten controls are checked, and how text vs filePath is resolved.

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 50%: 'text' is documented as 'systemd .service unit content', but 'filePath' has no description at all. The description mentions neither parameter and does not explain that they are alternative input modes or which one takes precedence, so it adds no meaning over the 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 gives a specific verb and resource ('Audit a Linux systemd .service unit') plus the scope of the analysis ('10 kernel sandboxing controls') and the output form ('security exposure score (0.1 to 10.0)'). That is enough to separate it from neighbors such as seccomp_apparmor_generate or docker_to_systemd, though no sibling is named 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?

Usage is only implied: an agent can infer you call this when you have a systemd unit and want a hardening score. There is no statement of when to prefer it over the related policy-generation or inspection tools, no prerequisites, and no exclusions.

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