Skip to main content
Glama
Sign In
SapperMCP

SapperMCP

by MasterX1582
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get Service Status

get_service_status

Retrieve detailed status for a named systemd service, including active/sub state, main PID, memory use, enablement, and recent status output.

Instructions

Detailed unit status: ActiveState/SubState, MainPID, memory, enablement, plus last status output lines.

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_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
userNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

No annotations are supplied, so the description bears the full burden; it partially discharges this by disclosing the returned status fields, which strongly implies a read-only inspection operation. It omits any statement about permissions, behavior for nonexistent or stopped units, or the fact that 'last status output lines' implies a bounded tail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence, front-loaded with the resource and then the field list; no wasted words. It is a noun fragment without a verb, but the content is efficient and well-ordered.

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?

An output schema exists, so explaining return values is not strictly required, yet the description spends its whole length on return fields while omitting parameter meaning. For a simple two-parameter inspection tool that is roughly adequate but leaves the 'user' flag unexplained.

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 0% across two parameters, and the description mentions neither 'name' nor 'user'. The 'user' boolean is especially opaque — it presumably selects a user-level unit scope — and the description does nothing to clarify it, leaving the agent to guess.

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?

Names a specific resource (a service/unit) and enumerates the exact status fields returned: ActiveState/SubState, MainPID, memory, enablement, and last status lines. This is enough to distinguish it from get_service_logs (log content) and manage_service (mutations), though it never explicitly contrasts with those siblings.

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?

The description contains no when-to-use guidance, no mention of prerequisites, and no pointer to alternatives such as get_service_logs for log inspection or manage_service for changes. An agent must infer usage purely from the field list.

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