Skip to main content
Glama

pbs_tfa_delete

Permanently remove a TFA entry from a PBS user. Run with confirm=false to preview lockout and takeover risks before executing.

Instructions

MUTATION (HIGH, IRREVERSIBLE): permanently remove one TFA factor from a user. HIGH because it WEAKENS authentication — an account-takeover enabler, and a lockout if it's the user's last factor on a TFA-required realm. Dry-run by default — the PLAN flags the permanence and the takeover/lockout risk. password, if supplied, is redacted identically to pbs_tfa_add's. confirm=True executes and returns a dict; synchronous, no UPID. Needs PROXIMO_PBS_* config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tfa_idYesTFA entry id to remove.
useridYesPBS user id, format 'user@realm'.
confirmNoFalse (default) returns a dry-run PLAN preview; True executes the mutation.
passwordNoThe ACTING user's own current password; redacted from all plans/logs/ledger.
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, the description fully discloses mutation, irreversibility, risk of weak auth/lockout, dry-run behavior, password redaction, sync execution, and config needs.

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?

Every sentence provides critical information; no fluff. Key warnings are 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?

Covers safety, behavior, all parameters, prerequisites, and return type. Output schema exists, so return info is sufficient.

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%, but description adds valuable context for password redaction, confirm's dry-run vs execution, and userid format.

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 it permanently removes a TFA factor, with explicit risk warnings. It distinguishes from other TFA tools by focusing on deletion.

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?

It explains dry-run by default and confirm=True for execution, and warns of risks. It does not directly compare to siblings 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