Skip to main content
Glama

devops-linux

seccomp_apparmor_generate

Generate an OCI seccomp.json syscall allowlist and AppArmor MAC confinement profile from a systemd .service unit.

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

Input Schema

NameRequiredDescriptionDefault
archNox86_64
textNosystemd .service unit content.
runtimeNoauto
filePathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It implies a pure generation/read-style operation and names the outputs, but says nothing about whether profiles are returned inline or written to disk, whether generation is deterministic, what happens if the unit cannot be parsed, or what permissions the tool needs.

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?

One dense, front-loaded sentence with no filler; the verb, both output artifacts, and the input source all appear immediately. Nothing is redundant or padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter generator with no annotations and no output schema, the description is too thin: the destination of the generated files, the meaning of 'filePath', and how 'runtime' and 'arch' affect the produced profiles are all unresolved. An agent could form the right intent but could easily call it incorrectly.

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 25%: only 'text' is documented (as the unit content). The description's phrase "from a systemd .service unit" maps loosely to 'text', but says nothing about 'arch', 'runtime', or — most critically — 'filePath', which is ambiguous between an input unit path and an output destination. With low coverage, the description needed to compensate and does not.

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?

States a specific verb ("Generate") and two concrete artifacts (an OCI seccomp.json syscall allowlist and an AppArmor MAC confinement profile) plus the exact input (a systemd .service unit). An agent can distinguish this from siblings like systemd_security_audit or docker_to_systemd without opening the schema, though it never names an alternative.

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

Usage Guidelines2/5

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

No explicit when-to-use, when-not-to-use, or prerequisite guidance. The only usage signal is implicit in the stated input (you have a .service unit and want confinement profiles); nothing tells the agent whether to prefer systemd_security_audit first, or whether runtime/arch choice matters for selection.

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