Skip to main content
Glama

pve_agent_info

Query a Proxmox guest's QEMU agent for system information (OS, hostname, users, network). Use exec-status with a PID to poll command completion.

Instructions

READ-ONLY: query the qemu-agent on a guest (ping, osinfo, hostname, users, exec-status, …).

Requires PROXIMO_ENABLE_AGENT=1, the VMID in PROXIMO_AGENT_ALLOWLIST, and a running guest agent inside the VM. No confirm needed — read-only. Returns a dict of the raw qemu-agent response fields for the chosen command; for command='exec-status', run pve_agent_exec first and pass its returned pid here to poll for completion.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pidNoProcess id returned by pve_agent_exec; required only when command='exec-status'.
nodeNoProxmox node name hosting the guest; auto-detected if omitted.
vmidYesNumeric VM ID of the guest to query via the qemu-agent.
commandNoqemu-agent query: ping, info, get-fsinfo, get-host-name, get-osinfo, get-time, get-timezone, get-users, get-vcpus, network-get-interfaces, get-memory-blocks, fsfreeze-status, or exec-status.info
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?

With no annotations, the description fully discloses the read-only nature, required environment variables, return format (dict of raw qemu-agent response), and the workflow for exec-status. This exceeds minimal expectations.

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 concise, uses bold for emphasis (READ-ONLY), avoids redundancy, and structures information in a logical flow: purpose, prerequisites, behavior, special case.

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 complexity of qemu-agent commands, the presence of an output schema, and the 100% schema coverage, the description covers all necessary aspects: prerequisites, read-only nature, return type, and the special exec-status workflow. It is complete for decision-making.

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?

The input schema already describes parameters thoroughly (100% coverage), but the description adds context by mentioning the exec-status pid linkage and listing example commands, enhancing understanding beyond the 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 is READ-ONLY for querying the qemu-agent on a guest, listing example commands (ping, osinfo, hostname, etc.) and distinguishing it from write-oriented sibling tools like pve_agent_exec or pve_agent_file_write.

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 provides explicit prerequisites (PROXIMO_ENABLE_AGENT, allowlist, running agent) and explains the special case for exec-status requiring prior pve_agent_exec call. However, it does not explicitly state when not to use this tool compared to other query tools.

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