Skip to main content
Glama

pbs_tape_key_create

Create a PBS tape encryption key to protect tape backups. Requires a password; use the resulting fingerprint to assign to a tape pool for encrypting future writes.

Instructions

MUTATION: create a PBS tape encryption key.

RISK_MEDIUM: creates a credential controlling future tape access. SECRET CONTRACT: key/ password are NEVER written to the audit ledger or returned in the dry-run PLAN — they are forwarded RAW only to the real PBS API on confirm=True (the create must actually work). confirm=True executes (POST /config/tape-encryption-keys, synchronous) and returns {"status": "ok", "result": ""} — the fingerprint is NOT secret, safe to record; assign it to a pool's encrypt field with pbs_tape_pool_create/pbs_tape_pool_update to actually encrypt future tape writes. Needs PROXIMO_PBS_* config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kdfNoKey derivation function: 'none', 'scrypt' (default), or 'pbkdf2'.
keyNoOptional: restore/re-create a key from this exported JSON string (300-600 chars) instead of generating a new one.
hintNoOptional password hint (no control characters, 1-64 chars).
confirmNoFalse (default) returns a dry-run PLAN only; True executes the creation.
passwordYesA secret password protecting the new key (min 5 chars). REQUIRED.
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 are provided, so the description shoulders full responsibility. It discloses that this is a mutation (MUTATION), risk medium (creates credential controlling future tape access), details the secret contract (key/password never written to audit ledger or returned in dry-run plan), describes the synchronous POST request, and explains the return value format.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear labels (MUTATION, RISK_MEDIUM, SECRET CONTRACT) and front-loads the most important information. It is somewhat lengthy but every sentence adds necessary context. Minor improvement possible by reducing redundancy.

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's complexity (mutation with dry-run, secret handling, fingerprint return), the description is complete. It explains the two execution modes, secret handling, the synchronous API call, the output schema (fingerprint), and how to use the result. No missing context.

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?

Input schema coverage is 100%, so baseline is 3. The description adds value by explaining the secret contract for key and password (never logged/returned), the confirm parameter's dry-run vs execution behavior, and how the returned fingerprint is not secret. This goes beyond the schema descriptions.

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 a PBS tape encryption key' and differentiates from sibling tools by describing how the resulting fingerprint is used with pbs_tape_pool_create/pbs_tape_pool_update. The verb 'create' and specific resource 'PBS tape encryption key' are clear.

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 the two modes (dry-run with confirm=False and execution with confirm=True), the required 'PROXIMO_PBS_* config', and the secret contract for handling sensitive parameters. It implicitly distinguishes from other tape key tools but does not explicitly state when not to use this tool.

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