Skip to main content
Glama
Sign In
mcp-systemctl

mcp-systemctl

by rileylsmith1997
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_service_logs

Retrieve recent journald logs for any systemd service. Filter by priority and control output line count.

Instructions

Retrieve recent journald log entries for a specific systemd service. Supports configurable line count (up to 5000) and optional priority filtering (emerg, alert, crit, err, warning, notice, info, debug).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "get_service_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesService name (e.g. 'sshd', 'cron', 'nginx.service')
linesNoNumber of recent log lines to retrieve (default: 50, max: 5000)
priorityNoFilter logs by minimum priority level

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It mentions retrieval and configurable parameters but lacks detail on side effects, permissions, or output format, though it adequately describes the basic behavior.

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?

Two sentences with no wasted words; every part adds value.

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 simple retrieval tool without output schema, the description covers purpose and key parameters, but could hint at return format or journald specifics for full completeness.

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

Parameters3/5

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

Schema description coverage is 100%, so baseline 3. The description restates line count and priority filtering without adding significant new meaning beyond the schema.

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 clearly states it retrieves journald log entries for a systemd service with a specific verb and resource, distinguishing it from sibling tools like get_service_status or service_control.

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?

The description implies usage for retrieving logs but does not explicitly state when not to use this tool or compare to alternatives; however, sibling tools are sufficiently different, making context clear.

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

Deploy Server

Other Tools