Skip to main content
Glama

pve_acme_account_delete

Deactivate and delete an ACME account from the certificate authority. Preview the irreversible deletion with a dry-run plan; confirm to execute.

Instructions

MUTATION: IRREVERSIBLE — deactivate and delete an ACME account from the CA. Dry-run by default.

HIGH risk: TLS lockout at cert expiry if this is the only account. The account key is destroyed — registering again with pve_acme_account_create creates a DIFFERENT CA account, not a restore of this one. The dry-run PLAN captures the current config as evidence only. confirm=True executes and returns {"status": "ok"}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the ACME account to deactivate and delete from the CA.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the irreversible deletion.
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 provided, the description fully bears the burden of disclosure. It declares the mutation is irreversible, details dry-run default and confirm execution, mentions key destruction, and notes the return value. This is 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?

The description is concise and well-structured, using bolded labels ('MUTATION', 'HIGH risk') to draw attention. Every sentence adds value, and the 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?

Given the high-risk, irreversible nature of the operation and the absence of annotations, the description covers all essential aspects: purpose, risk, behavior, parameter effects, and outcome. It is complete for an agent to use safely.

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% and the description does not add significant new parameter-level details beyond what the schema already provides. The dry-run and confirmation behavior is mentioned, but it only slightly reinforces the schema descriptions.

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 that the tool deactivates and deletes an ACME account from the CA, and distinguishes it from related tools like pve_acme_account_create and pve_acme_account_update by highlighting that re-registration creates a different account.

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 warns of high risk (TLS lockout), explains dry-run vs. confirm behavior, and states that creating a new account after deletion is not a restore. This provides clear when-to-use and when-not guidance.

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