Skip to main content
Glama

Run advanced spm command

spm_run_cli
Destructive

Run any non-interactive spm CLI command such as schedule, scale, rollback, apply, diff, or export. Use it to execute service management operations and return the command's text output.

Instructions

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.

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": {
      "arguments": "<arguments>"
    },
    "name": "spm_run_cli"
  }
}

Input Schema

NameRequiredDescriptionDefault
systemNoManage machine-wide services instead of the current user's. Requires root or Administrator; leave false unless the user asks for system scope.
argumentsYesArguments exactly as they appear after the spm executable, excluding --system. Example: ["schedule", "--name", "backup", "--cron", "0 2 * * *", "--", "backup.exe"].

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.9/5.0
Behavior5/5

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

The annotations already flag destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so safety is covered; the description goes further by disclosing the rejection behavior for interactive/watch modes, the text-only return format, the default user-scope target, and the root/Administrator prerequisite for system scope. That is genuine context an agent cannot get from the annotations or the two-parameter schema.

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?

Front-loaded with the core capability, then routing, then constraints, then privilege caveat. The subcommand list is long but load-bearing for scoping, and every remaining sentence carries a distinct rule with no filler.

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?

Although this is a broad, destructive, open-world tool with no output schema, the description states the return type (text output), the scope default, the privilege escalation requirement, the rejected mode classes, and a discovery mechanism for subcommand syntax. Nothing an agent needs in order to call it safely is missing.

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 description coverage is 100%, so both parameters are already documented, making 3 the baseline. The description adds operational meaning by noting arguments are passed exactly as after the executable (excluding --system) and by recommending the help pseudo-command to discover per-command options, which is real guidance beyond the schema. The only unadded detail is a concrete example of the system flag's failure mode, hence not a 5.

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?

A specific verb-plus-resource ("run any supported non-interactive spm CLI operation") followed by an explicit enumeration of the covered subcommands (schedule, signal, scale, rollback, apply, validate, diff, etc.). The sentence "Prefer focused tools when one exists" positions it as the general escape hatch relative to siblings like spm_start_service or spm_list_services, so an agent can tell what this tool is for without reading the schema.

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?

Explicit routing rule ("Prefer focused tools when one exists"), explicit exclusion ("Interactive editors and unbounded watch/follow modes are rejected"), an explicit pre-step ("run [\"help\", \"<command>\"] first"), and an explicit permission gate for the system flag. Both when-to-use and when-to-avoid are stated rather than inferred.

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