Skip to main content
Glama

pbs_node_service_control

Manage services on a Proxmox Backup Server node: start, stop, restart, or reload systemd services. Uses dry-run planning by default; set confirm=true to execute.

Instructions

MUTATION: start/stop/restart/reload a service on a PBS node. Dry-run by default — the PLAN flags lockout-class services (proxmox-backup/proxmox-backup-proxy/sshd/networking/ifupdown2/ chrony) as HIGH because stop/restart can sever management access or break backup jobs. There is NO auto-undo. confirm=True executes (POST /nodes/{node}/services/{service}/{action}) and returns {"status": "ok", "result": None}. Check current state first with pbs_node_service_status. Needs PROXIMO_PBS_* config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeNoPBS node name (or 'localhost').localhost
actionYesControl action: 'start', 'stop', 'restart', or 'reload'.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the service control.
serviceYessystemd service name to control, e.g. 'proxmox-backup-proxy' or 'sshd'.
proximo_targetNoWhich configured Proxmox target to run this call against — a target name from your multi-target config (a specific PVE/PBS/PMG/PDM box). Omit to use the single/default target from the environment; the selection applies only to this call.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations provided, so description carries full burden. It fully discloses mutation, dry-run behavior, lockout risks, no auto-undo, and return format on confirm.

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?

Concise, front-loaded with purpose and key behaviors. Every sentence adds essential information.

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?

Given no output schema and sibling tools, description covers mutation, dry-run, lockout risks, return on confirm, and suggests companion tool for status checks.

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% (baseline 3). Description adds value by explaining confirm behavior, dry-run output, and lockout service warning, going beyond schema.

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?

Clearly states verb (start/stop/restart/reload) and resource (service on PBS node). Distinguishes from sibling tools like pbs_node_service_status (check state) and pbs_node_services_list (list services).

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?

Provides use guidance: dry-run default, lockout service warnings, no auto-undo, suggests checking state first. Could explicitly exclude alternatives but context is clear.

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/john-broadway/proximo'

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