Skip to main content
Glama

pve_agent_info

Query a QEMU guest agent to retrieve OS info, hostname, users, network interfaces, and status. Read-only, no confirmation required.

Instructions

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

Requires PROXIMO_ENABLE_AGENT=1 and the VMID in PROXIMO_AGENT_ALLOWLIST. No confirm needed — read-only.

command: one of 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, exec-status. pid: required when command='exec-status' (the pid returned by pve_agent_exec).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pidNo
nodeNo
vmidYes
commandNoinfo
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?

With no annotations, the description carries full burden. It repeatedly emphasizes read-only behavior, mentions environment prerequisites, and notes that no confirm is needed. It does not cover error cases or rate limits, but the core behavioral traits (safe, read-only) are well-disclosed.

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?

The description is concise, with key information front-loaded (READ-ONLY). The list of commands is embedded in a paragraph, which could be more scannable, but overall it is efficient and contains no fluff.

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?

Given the presence of an output schema, the description adequately covers what the tool does, prerequisites, and parameter details. It could mention required vmid and optional node more explicitly, but the schema covers those. The description is complete for a read-only query tool.

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 description coverage is low (20%) for proximo_target only, but the description compensates by listing all possible values for 'command' and explaining the 'pid' parameter's dependency. This adds meaningful context beyond what the schema provides, though other parameters like vmid and node lack additional explanation.

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 for querying the qemu-agent on a guest, listing specific commands like ping, osinfo, etc. It distinguishes itself from sibling tools like pve_agent_exec by mentioning exec-status as a query and referencing the pid from pve_agent_exec, making the purpose unambiguous.

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 'No confirm needed', and it lists environment requirements (PROXIMO_ENABLE_AGENT, allowlist). It implies when to use this tool (for info queries) versus alternatives (pve_agent_exec for execution), but does not explicitly state when not to use it or compare directly, so it's clear but not exhaustive.

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