Skip to main content
Glama

Show service

spm_show_service
Read-only

Inspect one managed service's status, configuration, health, schedule, and file paths before changing or deleting it, or to learn how it was started.

Instructions

Show one managed service in detail as key-value text: status, enabled, PID, memory, restarts, uptime, last result and exit status, schedule, health, its saved configuration (command, working directory, restart policy and other options), and the paths of its unit and config files. Use it before changing or deleting a service, or to find out how a service was started; use spm_list_services to compare many services and spm_get_logs to see why one failed. Fails if the name is not managed by spm in that scope. Acts on the current user's services unless system is true; machine-wide services need root on Linux and macOS or an Administrator shell on Windows, so only use system when the user asks for it.

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

Input Schema

NameRequiredDescriptionDefault
nameYesManaged service name.
systemNoManage machine-wide services instead of the current user's. Requires root or Administrator; leave false unless the user asks for system scope.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / system / description
      Previous value: -"Manage machine-wide services instead of current-user services."New value: +"Manage machine-wide services instead of the current user's. Requires root or Administrator; leave false unless the user asks for system scope."
  2. First observedv0.3.9

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already mark this read-only, non-destructive and closed-world, but the description adds genuinely new behavioral facts: it fails when the name is not managed by spm in that scope, it acts on the current user's services by default, and system scope requires root on Linux/macOS or an Administrator shell on Windows. For a diagnostic read tool, that failure mode and privilege escalation constraint are exactly what an agent needs before invoking it.

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?

Purpose and scope are front-loaded in the first sentence, defaults and escalation constraints come last. The long field enumeration is dense but earns its place because no output schema exists. A slightly tighter first sentence would read better, but there is no filler or repetition.

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?

With no output schema, the description carries the return-value burden and does so by listing the returned fields and the unit/config file paths. It covers failure conditions, scope defaults, and sibling routing, leaving only minor gaps such as output formatting or whether the response is paginated. Rich enough for this simple two-parameter read tool.

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

Parameters4/5

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

Schema coverage is 100%, so the schema alone documents both parameters and baseline is 3. The description still adds meaning beyond it by stating the default scope ('acts on the current user's services unless system is true') and the concrete consequence of setting system — a privilege requirement and a platform-specific failure risk.

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?

States a specific verb and scope ('Show one managed service in detail') and enumerates exactly what is returned: status, enabled, PID, memory, restarts, uptime, last result, schedule, health, saved configuration, and file paths. It is immediately distinguishable from spm_list_services (compare many) and spm_get_logs (diagnose failures), which it names explicitly.

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?

Gives clear when-to-use guidance ('before changing or deleting a service', 'to find out how a service was started') and names the two alternatives with their conditions. It also gives a scope rule for the system parameter ('only use system when the user asks for it'). Lacks explicit when-not-to-use beyond those routing hints, so a 4 rather than 5.

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