Skip to main content
Glama

pbs_token_create

Create an API token for a PBS user. Confirm execution to obtain the secret key, which is returned only once.

Instructions

MUTATION (MEDIUM): create an API token for a PBS user.

Dry-run by default. PBS has NO privsep concept (unlike PVE) — the new token has NO privileges until an ACL entry grants it some (pbs_acl_update with auth_id='{userid}!{token_name}'). confirm=True executes and returns a dict whose result carries the token secret (value) ONCE — it is never written to the audit ledger and cannot be retrieved again (only regenerated via pbs_token_update, which invalidates it). Synchronous. Use pbs_user_tokens_list to see a user's existing tokens, or pbs_token_delete to remove one. Needs PROXIMO_PBS_* config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
digestNoOptional SHA256 config digest to prevent concurrent modifications.
enableNoWhether the token is usable immediately; None defers to PBS's default (enabled).
expireNoOptional token expiry as a Unix timestamp; None/0 means no expiry.
useridYesOwning PBS user, format 'user@realm'.
commentNoOptional free-text comment describing the token's purpose.
confirmNoFalse (default) returns a dry-run PLAN preview; True executes the mutation.
token_nameYesName for the new API token, unique per user.
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: it is a mutation (medium), synchronous, dry-run by default, token secret is returned only once and never written to audit ledger, cannot be retrieved again (only regenerated via pbs_token_update which invalidates it). It also notes that the new token has no privileges until an ACL entry grants them.

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 a single, well-structured paragraph that front-loads the purpose and mutation label. Every sentence adds value—no fluff or redundancy. It efficiently covers all key points.

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 complexity (8 parameters, output schema exists), the description covers all essential aspects: the dry-run mechanism, secret handling, prerequisite ACL configuration, related tools, and configuration requirements. It leaves no significant gaps for an agent to use it correctly.

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 all 8 parameters described. The description does not add extra per-parameter details beyond the schema, but it provides crucial context for the 'confirm' parameter (dry-run vs. execution) and overall behavior. Baseline 3 is appropriate given high schema coverage.

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 'create an API token for a PBS user' and labels it as 'MUTATION (MEDIUM)'. It clearly identifies the verb (create) and resource (API token), and is distinct from sibling tools like pbs_token_update, pbs_token_delete, and pbs_user_tokens_list.

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 provides comprehensive guidance: dry-run by default, confirm=True to execute, token has no privileges until ACL entry granted (pbs_acl_update), token secret is returned once and cannot be retrieved again. It also references pbs_user_tokens_list to see existing tokens and pbs_token_delete to remove, and mentions configuration requirements (PROXIMO_PBS_*).

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