Skip to main content
Glama

List node services

proxmox_list_node_services
Read-only

Lists Proxmox node system services with their running state and whether they are enabled, showing failed services first so you can quickly identify problems on a node.

Instructions

List the Proxmox-related system services on a node (pveproxy, pvedaemon, corosync, pve-cluster, chrony, sshd, postfix...) with their running state and whether they are enabled. Failed services are listed first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "proxmox_list_node_services"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeNoNode name. Defaults to PROXMOX_DEFAULT_NODE, or the only node on a single-node install. See proxmox_list_nodes.
fieldsNo
searchNoCase-insensitive substring filter on names, IDs, tags and similar fields

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description still adds real value by disclosing what each entry reports (running state, enabled flag) and the result ordering (failed services first), which a caller would otherwise have to discover empirically. It omits pagination and any permission prerequisites.

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?

Two tight sentences, front-loaded with the resource and its scope, with the return-shape and ordering facts last. The parenthetical service list is long but earns its place by defining exactly what counts as a "Proxmox-related" service.

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?

For a read-only list tool with no output schema, the description supplies the essentials: what is listed, what each row conveys, and how results are ordered. Annotations cover the safety profile, so nothing an agent needs in order to call this correctly is missing.

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

Parameters3/5

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

Schema coverage is 67%: node carries default-resolution guidance and search is documented, while fields has no description anywhere. The description itself says nothing about parameters, so it neither compensates for the undocumented fields parameter nor adds syntax beyond the schema — baseline 3.

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 resource ("List the Proxmox-related system services on a node") and pins the scope with concrete examples (pveproxy, pvedaemon, corosync, pve-cluster, chrony, sshd, postfix). That enumeration cleanly separates it from proxmox_list_ceph_services without needing to name it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the mention of running/enabled state and failed-first ordering suggests it is the go-to tool for checking service health on a node. There is no explicit when-to-use, no when-not, and no named alternative (e.g., journal/syslog tools for diagnosing why a service failed).

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