Skip to main content
Glama

List available package updates

proxmox_list_node_updates
Read-only

Lists available package updates on a Proxmox node, including installed and new versions, origin, priority, and counts. Refresh the node's package index first for current results.

Instructions

List the package updates available on a node (from the last package index refresh) with installed and new versions, origin and priority, plus counts. Run proxmox_refresh_node_updates first for fresh results. Installing updates is not available through the API.

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

Input Schema

NameRequiredDescriptionDefault
nodeNoNode name. Defaults to PROXMOX_DEFAULT_NODE, or the only node on a single-node install. See proxmox_list_nodes.
limitNoMaximum number of results (default 300)
fieldsNo
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

A4.2/5.0
Behavior4/5

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

Annotations already mark this read-only and closed-world, and the description adds real value on top: results are a snapshot of the last index refresh and may be stale, freshness requires a separate refresh call, and the update cannot be applied here. Return payload contents are also sketched (versions, origin, priority, counts).

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?

Three short sentences, front-loaded with what is listed, followed by the freshness prerequisite and the scope limit. Nothing is redundant or repeated from the schema.

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?

With no output schema, the description usefully enumerates the return contents and the staleness caveat, and all parameters are optional so the call is safe to make blind. The only gap is the unmentioned 'fields' parameter, which is a minor omission.

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 75% and the schema already documents node, limit and search, so the baseline applies. The description adds no meaning to any parameter and leaves the undocumented 'fields' array unexplained, so it neither compensates nor regresses.

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?

States a specific verb and resource ('List the package updates available on a node') and pins the data source ('from the last package index refresh'), which separates it from lookups like proxmox_get_node_package_versions that report installed versions only.

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?

Gives an explicit prerequisite ('Run proxmox_refresh_node_updates first for fresh results') and a scope boundary ('Installing updates is not available through the API'). It does not contrast against other update/package siblings, so it falls short of a full when/when-not guide.

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