Skip to main content
Glama

pbs_tfa_unlock

Clear a user's TOTP lockout caused by multiple failed attempts. Dry-run preview by default; set confirm=True to execute the unlock.

Instructions

MUTATION (HIGH): clear a user's TOTP lockout (PUT /access/users/{userid}/unlock-tfa — note the path lives under /access/users/, not /access/tfa/{userid}/). HIGH because it removes the anti-brute-force throttle guarding a 6-digit TOTP keyspace — an account-takeover enabler if the lockout was triggered by a real guessing attack. Dry-run by default. confirm=True executes and returns a dict whose result is a bool: whether the user was previously locked out. Synchronous. Needs PROXIMO_PBS_* config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
useridYesPBS user id to clear a TOTP lockout for, format 'user@realm'.
confirmNoFalse (default) returns a dry-run PLAN preview; True executes the mutation.
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 provided, so the description fully carries the burden. It discloses the mutation nature, high risk, default dry-run behavior, synchronous execution, return value format, and configuration requirement. This is thorough and transparent.

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 very concise, packing essential information (action, risk, default, return, config) into a few sentences without redundancy. Every sentence serves a purpose.

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?

Despite having an output schema, the description still provides useful context about the return value. It covers purpose, behavior, parameter semantics, and configuration needs. Complete for the tool's complexity.

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%, so baseline is 3. The description adds value by explaining the meaning of 'confirm' (dry-run vs. execution) and the userid format. It does not describe 'proximo_target', but the schema covers it. Overall, it enhances understanding beyond the schema.

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 explicitly states the action ('clear a user's TOTP lockout') and the resource (user), with the exact API path. It distinguishes itself from sibling tools by focusing on the unlock operation, clearly differentiating from other pbs_tfa_* tools.

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?

The description explains when to use (to clear a lockout) and when to exercise caution (if lockout was due to a real attack, it could enable account takeover). It also states the dry-run default and confirm=True for execution. It does not explicitly list alternatives, but the name and context make it 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