Skip to main content
Glama

pve_acme_plugin_create

Creates an ACME DNS challenge plugin for Proxmox VE. Dry-run by default; confirm to execute.

Instructions

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

Additive — does not affect any existing plugin. dns_api = DNS provider name (e.g. 'cf', 'route53'). Reference plugin_id from pve_node_acme_domains_set(plugin=...) to drive a DNS-01 challenge with it; to remove the plugin use pve_acme_plugin_delete. confirm=True executes and returns {"status": "ok"}; the default returns a dry-run PLAN dict. Smoke-confirm: POST body shape (id in body) against a live PVE instance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoPlugin-specific credential/config data (e.g. API tokens) required by the DNS provider.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the plugin creation.
disableNoSet to disable the plugin on creation; omit to leave it enabled.
dns_apiNoDNS provider API name for a DNS-01 challenge (e.g. 'cf', 'route53'); maps to PVE's 'api' field.
plugin_idYesIdentifier for the new ACME DNS challenge plugin (cluster/acme/plugins/{plugin_id}).
plugin_typeYesACME challenge plugin type, e.g. 'dns' for a DNS-01 challenge plugin.
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?

Despite no annotations, the description fully discloses mutation behavior, dry-run default, additive nature, and return types for dry-run (PLAN dict) and execution ({"status":"ok"}). No contradictions.

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 front-loaded with key info and structured but slightly verbose. Every sentence serves a purpose, though it could be tightened slightly without losing clarity.

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?

For a creation tool with output schema, the description covers dry-run vs execution, return format, and additive behavior. It provides sufficient context for correct usage.

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% with detailed parameter descriptions, so baseline is 3. The description adds value by explaining dns_api examples and how to use plugin_id with pve_node_acme_domains_set, which goes 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 'create an ACME DNS challenge plugin' with the specific verb 'create' and resource 'ACME DNS challenge plugin'. It distinguishes from siblings by mentioning removal via pve_acme_plugin_delete and implicitly from update.

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?

Provides explicit guidance: dry-run by default, use confirm=true for execution, and how to reference the plugin for DNS-01 challenges. Also mentions alternatives for removal.

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