Skip to main content
Glama

pve_node_cert_upload

Upload a custom TLS certificate to a Proxmox VE node to replace the default self-signed certificate.

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).

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. confirm=True to execute.

POST /nodes/{node}/certificates/custom Smoke-confirm: endpoint and body shape not live-verified.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNo
nodeNo
forceNo
confirmNo
restartNo
certificatesYes
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?

Details high risk, no undo, restart interruption, private key redaction policy, and smoke-confirm caveat. No annotations provided, so description fully covers behavioral aspects.

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?

Well-structured with clear sections, every sentence adds value, and critical information is front-loaded.

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 risks, behavior, redaction, revert, execution requirements, and testing limitation. Output schema exists, so return value details not needed. Complete for safe invocation.

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 low (14%), but description adds meaning for key parameters: key is private and redacted, confirm required, restart reloads pveproxy. Some parameters like force and node are not detailed, but focus on critical ones compensates.

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 it uploads a custom TLS certificate to a PVE node. It distinguishes from sibling tools like pve_node_cert_delete for reverting to self-signed.

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 mentions when to use (upload custom cert), high risk, and alternative revert method. Confirms execution requires confirm=True.

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