Skip to main content
Glama

ssh_service_status

Read-only

Report a systemd unit's loaded, active, and enabled state, plus journal tail, with fallbacks for non-systemd systems and permission-limited access.

Instructions

Reports one systemd unit: whether it is loaded, active and enabled, with the tail of its journal. A machine without systemd comes back as NOT CHECKED, never as a stopped service — that would read as an outage which is not there. Without sudo the journal is trimmed to what the profile user may see. For every failed unit at once, ssh_audit_baseline names them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sudoNoRead as root. Straight away for places a plain user cannot read (/root, /var/lib/docker); otherwise retry with true when the answer names what it could not read. Default: false Without it the journal comes back trimmed to what the profile user may see.
unitYesUnit name, e.g. "nginx" or "nginx.service".
sinceNoJournal window, as journalctl reads it: "1h ago", "today", "2026-08-19".
profileYesMachine name.
log_linesNoJournal lines returned. Default: 50

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
unitNo
enabledNo
outcomeNo
restartNo
sub_stateNo
recent_logNo
status_headNo
active_stateNo
restart_afterNo
Behavior5/5

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

Beyond the readOnlyHint annotation, it discloses the NOT CHECKED sentinel for non-systemd machines so the agent doesn't misread it as an outage, and clarifies how sudo affects journal trimming. These are valuable non-obvious behaviors.

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?

Four compact sentences, each earning its place: purpose, non-systemd sentinel, sudo behavior, and sibling routing. Key scoping information is front-loaded.

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

Completeness5/5

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

For a read-only status tool with a complete schema and an output schema, this description covers the important edge cases and the main alternative. Nothing essential is missing for correct invocation.

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 the schema already fully documents all parameters. The description reinforces the sudo/journal-trimming relationship but adds little new parameter-level meaning beyond that.

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 states a specific verb and resource: it reports one systemd unit and its loaded/active/enabled state plus journal tail. It also distinguishes itself from ssh_audit_baseline by making the single-unit scope explicit.

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

Usage Guidelines5/5

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

It explicitly routes the multi-failed-unit case to ssh_audit_baseline, telling the agent when not to use this tool. The opening 'Reports one systemd unit' also sets the single-unit scope clearly.

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/hypnosis/ssh-mcp-server'

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