Skip to main content
Glama

pve_tfa_delete

Delete a user's TFA factor after previewing the impact. Dry-run shows remaining factors and warns of account weakening; confirm executes the deletion.

Instructions

MUTATION (HIGH RISK): delete a user's TFA factor. Dry-run by default — the PLAN shows how many factors remain and warns this WEAKENS the account (and can lock the user out if it's the last factor on a TFA-required realm). password (if PVE requires it) is passed through but never logged. confirm=True executes and returns a dict; no UNDO (the factor must be re-enrolled).

NOTE (live-verified PVE 9.1.7): PVE requires a ticket-based login session — NOT an API token — to mutate TFA, returning 403 ... need proper ticket under token auth. Proximo is token-authed, so this delete will 403 on PVE; the read tools (pve_tfa_get/pve_tfa_list) work normally.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tfa_idYesId of the TFA factor to delete.
useridYesUser id whose TFA factor to delete, format 'user@realm'.
confirmNoFalse (default) returns a dry-run PLAN preview; True executes the mutation.
passwordNoThe user's current password, if PVE requires re-authentication for this mutation; never logged.
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 are provided, so the description carries full burden. It discloses high risk, dry-run behavior, plan preview, no undo, password handling (not logged), and the 403 limitation for token auth. This is comprehensive behavioral disclosure.

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?

Description is two paragraphs, front-loaded with key warnings and then a note. Every sentence adds essential information with no fluff. Efficient and well-structured.

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?

Covers all aspects: mutation risk, dry-run, confirm, password, lockout risk, auth limitation (403). With output schema existing, return values are explained. Complete for a high-risk mutation tool.

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 all parameters described. The description adds value by explaining the confirm parameter (dry-run vs execute), password's purpose, and proximo_target usage. But since schema already covers basics, score is slightly below 5.

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 the tool deletes a user's TFA factor, using the verb 'delete' and specifying the resource 'user's TFA factor'. It distinguishes from siblings pve_tfa_get and pve_tfa_list, which are read-only, by emphasizing this is a mutation.

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 when-to-use guidance: dry-run is default, warns about weakening account and potential lockout. Also includes a NOTE specifying that PVE requires ticket-based auth and token auth will fail, guiding the agent to avoid this tool with token auth.

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