Skip to main content
Glama

pve_acme_plugin_delete

Delete an ACME DNS challenge plugin. Dry-run returns a plan; confirm execution permanently removes it, risking cert auto-renewal failure.

Instructions

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

HIGH risk: cert auto-renewal breaks for every domain using this plugin — TLS lockout at cert expiry unless a fallback challenge method is configured. No UNDO primitive — recreate with pve_acme_plugin_create, but the credentials must be re-supplied by the caller. The dry-run PLAN captures the current config (credential redacted) as evidence only; confirm=True executes and returns {"status": "ok"}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoFalse (default) returns a dry-run PLAN only; True executes the deletion.
plugin_idYesIdentifier of the ACME DNS challenge plugin to delete.
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, but description fully discloses mutation, destructive nature, irreversibility, dry-run behavior, and risk of TLS lockout. Return value on confirm is specified.

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?

Concise, well-structured with clear sections. Every sentence adds value, no redundancy.

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 output schema exists and parameters fully described, the description covers necessary context: mutation, risk, dry-run, fallback, and return. Adequate for agent decision.

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 100% with good descriptions. Description adds context on dry-run and confirm effect, but does not significantly extend beyond schema. Still provides useful behavioral framing.

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?

Clearly states it deletes an ACME DNS challenge plugin, distinguishing it from create/update siblings. Uses verb 'delete' and resource 'ACME DNS challenge plugin'.

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 dry-run default, confirm parameter, high risk, no undo, and fallback alternatives. References sibling pve_acme_plugin_create for recovery.

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