Skip to main content
Glama

pbs_apt_changelog

Retrieve the upstream changelog for a package on a Proxmox Backup Server node. Specify the package name and optionally a version to view release notes.

Instructions

READ-ONLY: get a package's changelog text on a PBS node.

GET /nodes/{node}/apt/changelog?name=…[&version=…]. Smoke-confirm: shape not live-verified. The returned text is UPSTREAM/package-maintainer-authored (not Proxmox-authored) — classified ADVERSARIAL content (taint.ADVERSARIAL_TOOLS), like pve_apt_changelog and pmg_apt_changelog. Proxmox's API deliberately does not expose upgrade execution; the upgrade itself happens at your console. This tool governs visibility only. Needs PROXIMO_PBS_* config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesPackage name to fetch the changelog for (e.g. as listed by pbs_apt_updates_list).
nodeNoPBS node name; defaults to 'localhost' (standard single-node PBS name).localhost
versionNoSpecific package version to fetch the changelog for; omit for the latest available.
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?

No annotations provided, so description carries full burden. Declares READ-ONLY, warns about adversarial taint classification, notes shape not live-verified, and clarifies no upgrade execution. Sufficient for a read-only tool.

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?

Concise, every sentence adds value: purpose, endpoint, content classification, upgrade caveat, config requirement. Well-structured with clear headings and line breaks.

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?

With output schema present, return values need no explanation. Covers security, caveats, config. Adequate for the complexity of a read-only changelog fetch tool.

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 100%, baseline 3. Description adds no parameter details beyond the schema, which already documents all parameters. The endpoint pattern indirectly references 'node' and 'name', but no additional semantics.

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 'get a package's changelog text on a PBS node' with specific verb and resource. Provides API endpoint. Distinguishes from siblings via 'pbs' prefix and mentions sibling tools pve_apt_changelog and pmg_apt_changelog.

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?

Explicitly marks as READ-ONLY and clarifies it only provides visibility, not upgrade execution. Mentions config requirement. Lacks explicit when-not-to-use and direct comparison with siblings for selection, but context is clear.

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