Skip to main content
Glama
edymol

proxmox-mcp

by edymol

get_guest_status

Retrieve live status for a specific guest on a named Proxmox node, including state, uptime, CPU, memory, swap, disk, network, and HA state. Read-only and safe for stopped guests, which return a partial warning.

Instructions

One guest's live status, on exactly the node named.

Read-only and idempotent. Returns state, uptime, CPU, memory, swap, disk read and write, network in and out, and the high-availability state.

A stopped guest is an answer, not a failure: it returns this model with its state, a warning saying the live figures are not meaningful, and partial set. A vmid the cluster does not report on the node named raises a structured error naming both.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeYes
vmidYes
profileNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeYes
vmidYes
coresNo
sourceYes
statusYes
partialNo
profileYes
warningsNo
guest_typeYes
collected_atYes
uptime_secondsNo
disk_read_bytesNo
disk_used_bytesNo
swap_used_bytesNo
disk_total_bytesNo
disk_write_bytesNo
network_in_bytesNo
swap_total_bytesNo
cpu_used_fractionNo
high_availabilityNo
memory_used_bytesNo
network_out_bytesNo
memory_total_bytesNo
Behavior5/5

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

No annotations are present, so the description carries the full burden, and it excels: it declares read-only/idempotent behavior, enumerates returned metrics, and explains two edge cases (stopped guest and unknown vmid) with concrete responses. This is exemplary disclosure beyond typical descriptions.

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?

Four compact sentences, each adding distinct value: purpose, safety/return scope, and two edge cases. No filler or repetition; every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is well-covered in terms of behavior and return semantics, and an output schema exists. However, the undocumented 'profile' parameter and lack of alternative-tool guidance leave minor gaps, making it strong but not perfect.

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

Parameters2/5

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

The input schema provides no property descriptions (0% coverage), so the description must compensate. It gives some meaning to 'node' and 'vmid' through context, but the optional 'profile' parameter is never mentioned, leaving its semantics entirely undocumented.

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 phrase 'One guest's live status, on exactly the node named' clearly identifies the operation as retrieving live status for a single guest on a specific node. This distinguishes it from sibling tools like get_guest_config and guest_health_summary, and the tool name supplies the missing verb.

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?

The description does not explicitly name alternatives or state when to prefer this tool over siblings. It offers contextual signals like 'live status' and 'exactly the node named' that imply per-node monitoring use, but no exclusionary guidance is provided.

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/edymol/proxmox-mcp'

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