Skip to main content
Glama

pbs_tfa_add

Add a multi-factor authentication entry for a Proxmox Backup Server user. Supports TOTP, U2F, WebAuthn, recovery codes, and Yubico. Preview changes with dry-run before confirming.

Instructions

MUTATION (MEDIUM): add a TFA entry for a user. Dry-run by default.

SECRET-BEARING RESPONSE for type='recovery': confirm=True's result carries {"recovery": [], ...} — SERVER-GENERATED secret material, shown ONCE and never retrievable again. It is never written to the audit ledger (the detail= dict below never includes 'recovery'/'challenge'/'id'). password, if supplied, is UNCONDITIONALLY redacted identically to pbs_user_create's. For type='totp', the caller supplies the secret (via totp) — PBS does not generate one server-side for that type. confirm=True executes and returns a dict; synchronous, no UPID. Needs PROXIMO_PBS_* config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
totpNoFor type='totp': the totp: URI the caller generated (PBS does not generate this).
valueNoRegistration/verification value (e.g. the current TOTP code, or a WebAuthn/U2F challenge response).
useridYesPBS user id to add a TFA entry for, format 'user@realm'.
confirmNoFalse (default) returns a dry-run PLAN preview; True executes the mutation.
passwordNoThe ACTING user's own current password (re-authenticates the change); redacted from all plans/logs/ledger.
tfa_typeYesTFA entry type: 'totp', 'u2f', 'webauthn', 'recovery', or 'yubico'.
challengeNoFor u2f: the original challenge string being responded to.
descriptionNoOptional description to distinguish this entry from the user's others.
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 behavioral traits: mutation, dry-run, secret-bearing response for recovery, password redaction, synchronous execution, and configuration dependency. The return value and side effects are clearly described.

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 a single dense paragraph that could be more structured (e.g., with bullet points), but it is front-loaded with key info and every sentence adds necessary context. It is concise given the complexity.

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 complexity (9 parameters, output schema exists), the description covers mutation type, dry-run, secret material, password handling, synchronous execution, and configuration needs. It is complete for an agent to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds significant value beyond parameter descriptions: explains the meaning of 'recovery' type (server-generated secrets, shown once), contrasts with 'totp' (caller supplies secret), and clarifies password redaction and audit behavior.

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 verb 'add' and resource 'TFA entry for a user', distinguishes the tool from siblings like pbs_tfa_delete or pbs_tfa_update, and specifies the default dry-run behavior.

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?

Provides clear usage context: dry-run by default, confirm=True to execute, and specific guidance for type='recovery' and type='totp'. Lacks explicit when-not-to-use or alternative tool references, but the context is sufficient for typical use.

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