Skip to main content
Glama

pve_apt_repository_add

Add a standard APT repository to a Proxmox VE node configuration. Dry-run returns a plan; confirm=true executes the addition.

Instructions

MUTATION: add a standard repository to the configuration on a PVE node.

RISK_MEDIUM: adds a new package source — affects the NEXT upgrade's package provenance. CAPTURE: reads current repository state before planning (also readable directly via pve_apt_repositories_get); if unreadable -> complete=False. No automatic revert: removing an added repository requires pve_apt_repository_set to disable the resulting entry (there is no repository-delete endpoint). Proxmox's API deliberately does not expose upgrade execution; the upgrade itself happens at your console. This tool governs repo config only. Dry-run by default (returns a PLAN); confirm=True executes (PUT, Smoke-confirm) and returns {"status": "ok", "result": None}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeNoPVE node name to configure; defaults to the configured node if omitted.
digestNoExpected content digest of the repositories file, for optimistic-concurrency conflict detection.
handleYesHandle identifying the standard repository to add (as returned by pve_apt_repositories_get's standard-repos list, e.g. 'no-subscription').
confirmNoFalse (default) returns a dry-run PLAN only; True executes the addition.
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?

Discloses mutation, risk medium, effect on package provenance, dry-run behavior, no automatic revert, no delete endpoint, and that upgrades are not handled. With no annotations, the description fully covers behavioral traits.

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?

Well-structured with clear sections (MUTATION, RISK_MEDIUM, CAPTURE). Each sentence adds value, though slightly verbose. Front-loaded with key information.

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 complexity, output schema exists, and no annotations, the description is complete: covers purpose, usage, behavior, parameters, and return values implicitly (PLAN or status). 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 covers 100% of parameters with descriptions. The description adds value by explaining the handle comes from pve_apt_repositories_get, the confirm flag's effect, and the overall dry-run/confirm flow, going 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 adds a standard repository to a PVE node, using the verb 'add' and specifying the resource. It distinguishes from siblings by referencing standard repositories and mentioning pve_apt_repositories_get and pve_apt_repository_set.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit guidance: dry-run by default, confirm=True to execute. Mentions when to use (add standard repo), alternatives (pve_apt_repositories_get for reading, pve_apt_repository_set for modifying), and what the tool does not cover (upgrade execution).

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