Skip to main content
Glama

List TFA entries

proxmox_list_tfa
Read-only

Lists Proxmox VE users' two-factor factors and TFA lock-outs with type, description, creation time, and enabled state, without returning secrets.

Instructions

List users' second factors (TOTP, WebAuthn, recovery keys, Yubico) with type, description, creation time and enabled state, plus TFA lock-outs. No secrets are returned. Unlock a locked-out user with proxmox_unlock_tfa.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "proxmox_list_tfa"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNo
searchNo
useridNoUser ID in name@realm form, e.g. alice@pve or root@pam (see proxmox_list_users)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description usefully adds that no secrets are returned and that lock-outs are included in the result. It says nothing about result size, ordering, or whether listing requires elevated privileges, so added behavior beyond annotations is modest.

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?

Two sentences with zero filler; the payload (what is listed, what is included, what is not exposed) is front-loaded and the handoff to the unlock tool closes it out.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description does well to enumerate returned attributes and confirm no secrets leak, and it flags lock-out entries. However, for a 3-parameter tool with 33% schema coverage it leaves two parameters unexplained and says nothing about filtering or result limits.

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

Parameters2/5

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

Schema coverage is only 33%: userid is documented in the schema, but the fields and search parameters have no descriptions anywhere. The description's mention of 'type, description, creation time and enabled state' hints at selectable fields but never explains how the fields or search parameters work, so it does not compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List users' second factors') and enumerates the factor types (TOTP, WebAuthn, recovery keys, Yubico) plus the returned attributes and lock-outs. An agent can distinguish it from the surrounding list_* siblings by domain, though it never explicitly contrasts itself with them beyond the unlock handoff.

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?

Clear context: it is the tool for inspecting second factors and TFA lock-outs, and it routes the mutation case to proxmox_unlock_tfa. It does not state exclusions (e.g., whether it covers all users or a subset by default), so it falls short of explicit when/when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools