Skip to main content
Glama

pve_apt_update_refresh

Refresh the APT package index on a PVE node. Dry-run by default; confirm to execute and resynchronize index cache.

Instructions

MUTATION: resynchronize the APT package index on a PVE node (apt-get update).

RISK_LOW: no package state change — refreshes the local index cache only. Proxmox's API deliberately does not expose upgrade execution; the upgrade itself happens at your console. This tool governs visibility only — it does NOT install or upgrade any package. Idempotent — safe to re-run any time. Dry-run by default (returns a PLAN); confirm=True executes (POST, Smoke-confirm) and returns {"status": "submitted"|"ok", "result": <task UPID | None>}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeNoPVE node name to refresh; defaults to the configured node if omitted.
quietNoIf True, ask Proxmox to omit progress output suitable only for interactive logging.
notifyNoIf True, ask Proxmox to send a notification email about newly available packages.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the index refresh.
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
Behavior5/5

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

No annotations provided, but the description fully covers behavior: mutation, low risk, no package change, idempotent, dry-run default, execution flow, and API limitation about upgrades. No contradictions.

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 paragraph with clear tags (MUTATION, RISK_LOW) and line breaks. Every sentence adds value; front-loaded with purpose and risk. No fluff.

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?

Given no annotations and an output schema, the description is comprehensive. Covers mutation, risk, idempotency, dry-run, execution, and API context. No gaps.

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 already describes all 5 parameters with good coverage (100%). The description adds workflow context: dry-run vs execute, and the effect of confirm. Adds value beyond schema.

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 refreshes the APT package index on a PVE node, with explicit contrast to upgrades ('does NOT install or upgrade any package'). It distinguishes from siblings like pve_apt_updates_list by focusing on refresh 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?

Provides clear context: use for refreshing the index, not for upgrades. Explains dry-run default and confirm parameter for execution. Does not explicitly list when not to use or alternatives beyond upgrade, but the workflow is implied.

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