Skip to main content
Glama

Get package changelog

proxmox_get_package_changelog
Read-only

Retrieve a package's changelog on a Proxmox node to see what an update changes, with optional version selection and character truncation.

Instructions

Get the changelog of a package available on a node, e.g. to see what an update to pve-manager or proxmox-kernel changes. Truncated to max_chars.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "package": "<package>"
    },
    "name": "proxmox_get_package_changelog"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeNoNode name. Defaults to PROXMOX_DEFAULT_NODE, or the only node on a single-node install. See proxmox_list_nodes.
packageYesPackage name, e.g. pve-manager
versionNoPackage version (default the candidate version)
max_charsNoTruncate the text to this many characters (default 20000)

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, openWorldHint=false and idempotentHint=false, so the safety profile is covered. The description adds that output is text truncated at max_chars, which is useful behavioral context, but says nothing further about format, authentication, or failure modes (e.g. unknown package or version).

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?

Two short sentences, front-loaded with the core action and followed by a concrete use case; nothing is wasted. The truncation note is slightly redundant with the schema but is placed logically.

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 simple read-only fetch with full schema coverage, no output schema and no nested objects, the description covers what is needed to call it correctly. The only minor gap is that it doesn't characterize the return text (plain changelog vs. formatted), which an agent might want to know.

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%, so all four parameters are already documented in the input schema, including defaults for node, version and max_chars. The description only echoes the truncation behavior, adding no semantics beyond the schema — the baseline 3 applies.

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 ('Get the changelog of a package available on a node') and illustrates the outcome with concrete examples (pve-manager, proxmox-kernel). It is clearly distinct from the sibling version-listing tool, though it never names that sibling 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?

The clause 'e.g. to see what an update ... changes' supplies a motivating use case, which is more than nothing. However, there is no guidance on when to prefer proxmox_get_node_package_versions instead, no prerequisites, and no exclusions.

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