Skip to main content
Glama

pve_tfa_list

List all per-user two-factor authentication entries across the Proxmox VE cluster. Returns configured TFA entries in a read-only format.

Instructions

List all per-user TFA (two-factor) entries across the cluster (read-only). Returns the configured TFA entries; the exact shape varies by PVE version (typically per-user with a nested entries list of factor type/id). Use pve_tfa_get for one user's entries; use pve_tfa_delete (confirm=True) to remove a factor (RISK_HIGH).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, but the description discloses that the output shape varies by PVE version, which is important for the agent. It also states read-only behavior. No mention of authorization or rate limits, but for a simple list tool, this is adequate.

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 three sentences, front-loaded with the core purpose, then adding version variability and sibling references. No wasted words.

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 tool is a simple listing with one optional param and an output schema (assumed present), the description covers return shape variance, alternatives, and safety. It is complete for an agent to use effectively.

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% with a well-described optional parameter proximo_target. The description adds no additional parameter guidance, so baseline 3 is appropriate.

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 lists all per-user TFA entries across the cluster, specifies it is read-only, and distinguishes itself from sibling tools pve_tfa_get and pve_tfa_delete.

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?

The description explicitly tells the agent when to use alternatives: pve_tfa_get for a single user, pve_tfa_delete for removal (with risk note). It also notes the operation is read-only.

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