Skip to main content
Glama

pve_guest_status

Retrieve operational status and resource utilization of a Proxmox guest. Returns runtime metrics like CPU, memory, disk, network, and uptime.

Instructions

Read the operational status and current configuration of a single guest (kind='lxc' or 'qemu') (read-only). Returns the guest's runtime state and resource utilization (CPU/memory/disk/network/uptime) — operational metrics, not its stored configuration. Use pve_guest_config_get for the full configuration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoGuest type: `lxc` for a container or `qemu` for a VM.lxc
nodeNoPVE node the guest runs on. Omit to resolve it automatically from the cluster.
vmidYesNumeric ID of the guest — VMID for a QEMU VM or CTID for an LXC container.
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
Behavior4/5

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

No annotations are provided, so the description carries full burden. It states the tool is read-only, returns operational metrics (CPU/memory/disk/network/uptime), and clarifies it is not stored configuration. It could mention it does not modify anything, but that is implied.

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?

The description is two sentences, front-loaded with purpose, and no unnecessary words. Highly concise and well-structured.

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 the tool's moderate complexity and presence of output schema, the description sufficiently covers purpose, return value (operational metrics), and how to get full configuration. Complete for agent usage.

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 100%, so baseline is 3. The description mentions kind='lxc' or 'qemu' but that information is already in the schema. No additional semantics added 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?

The description clearly states the tool reads operational status of a single guest, specifies guest types (lxc or qemu), and distinguishes itself from pve_guest_config_get by noting it returns runtime state not configuration.

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?

The description explicitly says 'read-only' and directs use of pve_guest_config_get for full configuration, providing clear context. However, it does not mention when to avoid using this tool or other alternatives, but the guidance is sufficient.

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