Skip to main content
Glama

pve_acme_plugin_update

Update an ACME DNS challenge plugin's configuration and preview changes with a dry-run plan to avoid breaking certificate renewal.

Instructions

MUTATION: update an ACME DNS challenge plugin. Dry-run by default.

MEDIUM risk — invalid new credentials break cert renewal for every domain using this plugin at the next attempt. To remove a plugin instead use pve_acme_plugin_delete. The dry-run PLAN includes the plugin's current config with any DNS-provider credential redacted; confirm=True executes and returns {"status": "ok"}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoNew plugin-specific credential/config data; omit to leave unchanged.
digestNoConfig digest for optimistic-locking the update against concurrent changes; omit to skip the check.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the update.
disableNoSet to enable/disable the plugin; omit to leave unchanged.
dns_apiNoNew DNS provider API name for a DNS-01 challenge; maps to PVE's 'api' field. Omit to leave unchanged.
plugin_idYesIdentifier of the existing ACME DNS challenge plugin to update.
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 exist, so description carries full burden. It discloses mutation, dry-run default, risk of breaking cert renewal, plan redaction, and confirm behavior. Comprehensive.

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?

Four sentences, efficiently structured. Front-loaded with 'MUTATION: update...', then risk, sibling, and behavior. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given output schema exists, return values are handled. Description covers dry-run plan and confirm response, plus risk. Missing prerequisites like needing an existing plugin, but still strong.

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?

Schema coverage is 100%, so baseline 3. Description adds workflow context (dry-run vs confirm) but no per-parameter details beyond schema. Adequate but not exceptional.

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 states a specific verb ('update') and resource ('ACME DNS challenge plugin'), and distinguishes from sibling tool pve_acme_plugin_delete. The 'dry-run by default' adds clarity.

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?

Explicitly tells when to use an alternative: 'To remove a plugin instead use pve_acme_plugin_delete'. No explicit when-not-to-use beyond that, but context is clear.

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