Skip to main content
Glama

Get Proxmox package versions

proxmox_get_node_package_versions
Read-only

Lists installed versions of key Proxmox packages on a node, including the running kernel, to check package state like pveversion -v.

Instructions

List the installed versions of the important Proxmox packages on a node (like pveversion -v), including the running kernel.

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_get_node_package_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeNoNode name. Defaults to PROXMOX_DEFAULT_NODE, or the only node on a single-node install. See proxmox_list_nodes.
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

A3.5/5.0
Behavior3/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 adds that results include the running kernel and mirror `pveversion -v` output, but it does not clarify what 'important' packages means (curated subset?) or how the `search` filter interacts with the listing.

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?

A single front-loaded sentence with an efficient parenthetical CLI analogy; no wasted wording. Minor deduction because 'important' is left undefined rather than specified.

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?

For a two-parameter read-only tool with full schema coverage and no output schema, the definition gives enough to call it and anticipate the shape of results via the pveversion analogy. Only the ambiguity around which packages count as 'important' leaves a small gap.

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 description coverage is 100% with only two optional parameters, so the schema already documents node resolution and the case-insensitive substring filter. The description adds nothing about either parameter, leaving baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 installed versions of the important Proxmox packages on a node', and the `pveversion -v` analogy makes the exact scope concrete. It implicitly separates itself from update-oriented siblings, though it does not name them explicitly.

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 — an agent can infer this is the tool for auditing what is currently installed. There is no explicit when-to-use/when-not guidance, and no pointer to a distinct sibling such as the node updates listing for pending upgrades.

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