Skip to main content
Glama

pve_node_cert_upload

Upload a custom TLS certificate to a Proxmox VE node. To avoid lockout, use dry-run mode before confirming.

Instructions

MUTATION: upload a custom TLS certificate to a PVE node.

RISK_HIGH, NO UNDO. A malformed cert/key can lock you out of the PVE web UI and API. restart=True reloads pveproxy after upload (brief service interruption). To view the node's currently configured certs use pve_node_certificates.

PRIVATE KEY REDACTION: the 'key' param is a TLS private key (secret). It is UNCONDITIONALLY redacted — it NEVER appears in the plan, change, current state, detail, or ledger (regardless of redact_ledger setting). Only {"key": "[redacted]"} is recorded. The cert body (certificates) is public and may appear in plans/logs.

Revert: re-upload a correct cert, or use pve_node_cert_delete to revert to self-signed. Dry-run by default (returns a PLAN); confirm=True executes (POST, Smoke-confirm) and returns {"status": "ok", "result": <dict | None>}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoPEM-encoded TLS private key matching the certificate; a secret, unconditionally redacted in all output.
nodeNoPVE node name to upload the certificate to; defaults to the configured node if omitted.
forceNoIf True, overwrite an existing custom certificate without requiring it be replaced explicitly.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the certificate upload.
restartNoIf True, reload pveproxy after upload to apply the new certificate immediately (brief service interruption).
certificatesYesPEM-encoded certificate chain (public, may appear in plans/logs).
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; description carries full burden. Discloses mutation risk, no undo, potential lockout, restart interruption, unconditional private key redaction, and dry-run/execute behavior comprehensively.

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 (purpose, risk, usage, redaction, revert). Front-loaded but slightly long; every sentence adds value, though minor trimming possible.

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?

Covers purpose, risk, alternatives, redaction policy, revert options, dry-run/execute behavior, and return format. No missing context for a mutation tool with high risk and sensitive data.

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 coverage is 100%, baseline 3. Description adds context about redaction of the 'key' parameter and restart behavior, slightly improving over schema-only info.

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 'MUTATION: upload a custom TLS certificate to a PVE node', providing a specific verb and resource. It distinguishes from siblings like pve_node_certificates (view) and pve_node_cert_delete (revert).

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?

Explicitly describes dry-run vs. execution (confirm=True), warns about risks, and names alternative tools for viewing (pve_node_certificates) and reverting (pve_node_cert_delete), giving clear when-to-use guidance.

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