Skip to main content
Glama

pve_node_acme_domains_set

Set ACME account and domain list on a Proxmox VE node for certificate issuance. Use with DNS plugin for DNS-01 or standalone for http-01; dry-run by default, confirm to apply.

Instructions

MUTATION: set a node's ACME account + domains (PUT /nodes/{node}/config). Dry-run by default.

The "what to issue" half of an ACME cert: pair with pve_acme_account_create + pve_acme_plugin_create, then issue with pve_acme_cert_order. plugin= uses a DNS-01 challenge (written as acmedomain0..N=domain=...,plugin=...); omit plugin for standalone http-01 (domains ride in acme=...,domains=...). REPLACE semantics: stale acmedomainN entries are removed, not merged. MEDIUM — config only, no cert is issued by this step. confirm=True executes and returns {"status": "ok"}; the default returns a dry-run PLAN dict. Smoke-confirm: node-config body shape against a live PVE instance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeNoTarget PVE node name; omit to use the configured default node.
pluginNoACME DNS plugin ID for a DNS-01 challenge; omit to use standalone http-01 instead.
accountYesName of the ACME account (created via pve_acme_account_create) to associate with the node.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the node config change.
domainsYesDomain names to request a certificate for; replaces any existing acmedomainN entries on the node.
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?

With no annotations, the description fully discloses behavioral traits: dry-run by default, REPLACE semantics (stale entries removed), MEDIUM impact (config only, no cert issuance), and behavior of confirm parameter (dry-run plan vs status ok). The smoke-confirm hint adds extra transparency.

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, front-loading key info (mutation, dry-run) and then detailing workflow, parameter usage, and behavior. It is dense but every sentence adds value. Slightly long with three paragraphs, but still efficient.

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 complexity of ACME workflows and the tool's role, the description is remarkably complete. It covers workflow positioning, parameter behavior, return types (PLAN dict or status ok), and replace semantics. The presence of an output schema further supports completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds significant meaning: explains how plugin and confirm parameters work in context, clarifies that node defaults to configured default, and links domains to acmedomainN entries. This enhances understanding beyond the 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 it is a mutation to set a node's ACME account and domains, distinguishing it from other ACME tools like account creation, plugin creation, and cert ordering. It specifies the HTTP method (PUT) and resource, making the purpose unambiguous.

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 explicit workflow instructions: pair with pve_acme_account_create and pve_acme_plugin_create, then issue with pve_acme_cert_order. It explains when to use plugin (DNS-01) vs omit (HTTP-01). However, it does not explicitly state when not to use this tool, but the context is strong.

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