Skip to main content
Glama

pbs_token_update

Update a PBS API token's metadata: change enable, expiry, comment; regenerate the secret with confirmation. Dry-run by default.

Instructions

MUTATION: update a PBS API token's metadata. Dry-run by default.

RISK IS CONDITIONAL: regenerate=False is MEDIUM (metadata-only); regenerate=True is HIGH — it issues a brand-new secret and invalidates the OLD one IMMEDIATELY, with no grace period, breaking any integration still using it. When regenerate=True, confirm=True's result carries the NEW secret ONCE (key 'secret') — same never-in-ledger contract as pbs_token_create: the detail dict passed to the audit ledger never contains it.

confirm=True executes and returns a dict; synchronous, no UPID. Needs PROXIMO_PBS_* config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
digestNoOptional SHA256 config digest to prevent concurrent modifications.
enableNoWhether the token is usable; False disables it immediately. Omit to leave unchanged.
expireNoToken expiry as a Unix timestamp; omit to leave unchanged.
useridYesOwning PBS user, format 'user@realm'.
commentNoOptional free-text comment; omit to leave unchanged.
confirmNoFalse (default) returns a dry-run PLAN preview; True executes the mutation.
regenerateNoIf True, issue a BRAND-NEW secret and invalidate the old one immediately (RISK_HIGH — any system using the old token loses access instantly).
token_nameYesName of the API token to update.
delete_propsNoProperty names to clear: only 'comment' is supported by PBS on this endpoint.
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?

Thoroughly discloses behavioral traits: mutation, dry-run by default, conditional risk of regenerate (MEDIUM vs HIGH), immediate invalidation on regenerate=True, one-time secret exposure on confirm=True, synchronous execution, and config requirement. No annotations exist, so description carries full burden and excels.

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?

Efficient and well-structured. First sentence defines purpose, then risk explanation, then details on confirm and config. No redundant sentences; each adds value.

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

Completeness4/5

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

Given good schema descriptions and output schema presence, description covers core behavioral aspects adequately. Missing details on parameters like enable/expire/comment are handled by schema. Could mention output shape slightly more, but sufficient for a complex tool.

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% with detailed field descriptions. Description adds risk context for regenerate and confirm parameters beyond schema, including behavioral implications and the one-time secret contract. Does not explain every parameter but compensates by focusing on critical 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?

Description clearly states it's a mutation for updating PBS API token metadata, using a specific verb and resource. It distinguishes itself from sibling token tools by focusing on metadata updates and explaining the dry-run default.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit comparison to sibling tools like pbs_token_create or pbs_token_delete. Usage context is implied through risk explanation, but no clear when-to-use or when-not-to-use guidance.

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