Skip to main content
Glama

pbs_node_config_set

Update Proxmox Backup Server node-wide configuration. Dry-run shows changes; confirm executes to set or delete properties like TLS ciphers, proxy, ACME domains, and more.

Instructions

MUTATION: update PBS node-wide config.

RISK_HIGH, uniform across the whole PUT: ciphers-tls-1.2/1.3 misconfiguration can make the API/web proxy refuse ALL TLS connections (lockout-class, mirrors network_reload/cert_upload); http-proxy misconfiguration can silently break outbound connectivity for notifications/ACME renewal/subscription-check; acme/acmedomain0-4 misconfiguration can break automatic certificate renewal — see proximo.pbs_admin module docstring's RISK RATING section. Dry-run by default (captures current config into the PLAN, http-proxy masked defensively); confirm=True executes (PUT /nodes/{node}/config, synchronous — PBS returns null) and returns {"status": "ok", "result": None}. No snapshot primitive — revert by re-applying the captured current config. Needs PROXIMO_PBS_* config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
acmeNoACME account assignment, pre-formatted per PBS's compound syntax, e.g. 'account=myaccount'.
nodeNoPBS node name (or 'localhost').localhost
deleteNoProperty names to clear: any of acme/acmedomain0-4/http-proxy/email-from/ciphers-tls-1.3/ciphers-tls-1.2/default-lang/description/task-log-max-days/consent-text/location.
digestNoOptimistic-lock: 64-char lowercase hex SHA-256 of the config PBS last returned.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the update.
locationNoFree-text location label for this PBS instance.
email_fromNoFrom-address for node-generated e-mail (2-64 chars).
http_proxyNoHTTP proxy configuration '[http://]<host>[:port]'. May embed 'user:pass@' credentials per standard URL syntax — masked defensively in the returned Plan.
acmedomain0NoACME domain 0, pre-formatted e.g. 'domain=example.com,alias=other.com,plugin=cf'.
acmedomain1NoACME domain 1, same compound format as acmedomain0.
acmedomain2NoACME domain 2, same compound format as acmedomain0.
acmedomain3NoACME domain 3, same compound format as acmedomain0.
acmedomain4NoACME domain 4, same compound format as acmedomain0.
descriptionNoNode comment (multiple lines allowed).
consent_textNoConsent banner text (<=65536 chars).
default_langNoUI language code (closed enum, e.g. 'en', 'de', 'fr').
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.
ciphers_tls_1_2NoOpenSSL cipher list for TLS <= 1.2. Misconfiguration can break ALL TLS connections to the API/web proxy.
ciphers_tls_1_3NoOpenSSL ciphersuite list for TLS 1.3. Misconfiguration can break ALL TLS connections to the API/web proxy.
task_log_max_daysNoMaximum days to keep task logs (>=0).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

In the absence of annotations, the description fully discloses critical behaviors: it's a mutation, synchronous, returns null with status ok, no snapshot primitive (revert by re-applying current config), and details specific risks for ciphers, http-proxy, and acme parameters. Dry-run behavior and masking of http-proxy are also noted.

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?

The description is well-structured, starting with a clear purpose statement, followed by risk warnings, usage instructions, and reversion advice. It is slightly long but each sentence adds value; no unnecessary repetition.

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 the tool's complexity (20 parameters, high risk) and the presence of an output schema, the description covers all essential aspects: how to use, risks, dry-run vs. confirm, reversion method, and prerequisites. References to an external docstring for detailed risk ratings further enhance completeness.

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?

The input schema has 100% description coverage, so the baseline is 3. The description adds context by grouping risky parameters (ciphers, http-proxy, acme) and noting http-proxy masking, but does not significantly enhance individual parameter semantics beyond what the schema already provides.

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's purpose: 'MUTATION: update PBS node-wide config.' It uses a specific verb ('update') and resource ('PBS node-wide config'), distinguishing it from the get-only sibling pbs_node_config_get. The MUTATION label reinforces its write nature.

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?

The description provides guidance on dry-run vs. confirm execution and warns about high-risk parameter misconfigurations. However, it does not explicitly state when not to use the tool or compare it to alternative tools for similar tasks, such as pbs_node_cert_upload for certificate issues.

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