Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Use spm tools to inspect and manage persistent services. Prefer focused read-only tools first, then focused write tools. Use spm_run_cli only for advanced operations without a dedicated tool. Confirm the target and scope before state-changing or destructive calls.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
spm_list_servicesA

List every service spm manages in the chosen scope with its live state. Call this first to see what is running, to find an exact service name, or to confirm the effect of a create, start, stop or delete; use spm_show_service for one service's full configuration. Returns structuredContent.services with one entry per unit (a multi-instance service has one entry per instance): name, status, active_state, sub_state, health, pid, cpu_percent, memory_bytes, restarts, enabled, uptime_seconds, and schedule for scheduled jobs. Values the platform cannot report are null. An empty array means no services exist 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.

spm_show_serviceA

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.

spm_get_logsA

Read recent log lines from one or more managed services. Use it to check that a service started cleanly, to find why it crashed or keeps restarting, or to read its output such as URLs, ports and errors; use spm_doctor instead when spm itself or the service manager seems broken. Returns at most lines entries (default 100) as text; with several names, their entries are combined. Set health=true to read health-check output instead of service output. It never follows logs, so call it again to see newer lines. 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.

spm_doctorA

Check that spm can manage services in the chosen scope: whether the service manager is reachable and recent enough, the unit directory, log access, login persistence and the spm executable; the exact checks depend on the platform. Use it when a create, start or list call fails unexpectedly, or before the first service on a new machine; use spm_get_logs for problems inside one service. Returns one line per check marked ok, info, warn or fail, with details on what is wrong. 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.

spm_create_serviceA

Create a new persistent service from a command and start it immediately. By default it restarts when it exits and starts again at login, so use it instead of running long-lived processes in the background (&, nohup, start /b) for dev servers, workers and bots that must outlive the session. Use spm_start_service or spm_enable_service for a service that already exists. If the name is taken the call fails; set force=true only after the user agrees to replace that service. Put secrets in an env_file, never in command arguments. Afterwards, call spm_get_logs to confirm it started. 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.

spm_start_serviceA

Start an existing managed service that is stopped. It does not change whether the service starts at login; use spm_enable_service to start it and turn that on, or spm_create_service for a service that does not exist yet. A service that is already running is left as it is; use spm_restart_service to pick up code or configuration changes. 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.

spm_restart_serviceA

Stop and start a managed service so it picks up new code, configuration or environment. The process gets a new PID and is briefly unavailable; a multi-instance service is restarted one instance at a time so the others keep serving. A stopped service is simply started. 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.

spm_stop_serviceA

Stop a running managed service for now. It keeps its definition and still starts again at the next login or boot if it is enabled; use spm_disable_service to keep it stopped, or spm_delete_service to remove it. For a scheduled job, this also stops its timer. 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.

spm_enable_serviceA

Turn on start at login or boot for an existing managed service, and start it now. Use it to undo spm_disable_service; use spm_start_service to run a service now without changing its startup setting. For a scheduled job, this re-enables its timer. 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.

spm_disable_serviceA

Stop a managed service and turn off start at login or boot, so it stays stopped until enabled again. Its definition is kept and spm_enable_service brings it back. Use spm_stop_service for a temporary stop, or spm_delete_service to remove it completely. For a scheduled job, this disables its timer. 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.

spm_delete_serviceA

Stop a managed service and permanently remove its definition, saved configuration and companion units such as schedules and health checks. This cannot be undone; the service must be created again with spm_create_service. Confirm the exact name and scope with the user first, and prefer spm_stop_service or spm_disable_service when the user may need it again. 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.

spm_run_cliA

Run any supported non-interactive spm CLI operation, including schedule, signal, scale, set, unset, clone, history, rollback, apply, validate, diff, native inspection, security analysis, export, health, and import. Prefer focused tools when one exists. Interactive editors and unbounded watch/follow modes are rejected. Returns the command's text output; run ["help", ""] first to see a command's options. 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.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 12 tools

Disambiguation5/5

Each tool targets a distinct service-management action; start vs enable and stop vs disable are explicitly differentiated in their descriptions, and spm_run_cli is positioned as a fallback only when no focused tool exists. No two tools appear to do the same thing.

Naming Consistency4/5

All tools use the spm_ prefix and snake_case, with a consistent verb_noun pattern for lifecycle and query operations. spm_doctor is the only noun-only name, a minor deviation from the otherwise predictable convention.

Tool Count5/5

Twelve tools is well within the appropriate range for a service manager, covering discovery, inspection, lifecycle, diagnostics, and an escape hatch without bloat. Each tool earns its place.

Completeness5/5

The set covers create/read/update/delete and full lifecycle operations (start, stop, restart, enable, disable), plus logs and diagnostics; configuration updates and advanced operations are available through spm_run_cli. No obvious dead ends exist for the stated domain.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues