Skip to main content
Glama

pbs_encryption_key_create

Create a Proxmox Backup Server client encryption key by specifying a key_id and optionally providing key material; use confirm=True to execute.

Instructions

MUTATION: create a PBS client encryption key.

RISK_MEDIUM: creates a credential controlling future client-side encryption capability. SECRET CONTRACT: key (if given) is NEVER written to the audit ledger or the dry-run PLAN — forwarded RAW only to the real PBS API on confirm=True. SCHEMA QUIRK: this endpoint returns null — unlike the tape-encryption-keys plane, NO fingerprint comes back; check pbs_encryption_key_list afterward for the assigned fingerprint/hint/kdf, if any. confirm=True executes (POST /config/encryption-keys, synchronous) and returns {"status": "ok", "result": None}. Needs PROXIMO_PBS_* config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoOptional: import this key material instead of having PBS generate a fresh one. No length bound (unlike the tape-encryption-keys plane's 300-600 char requirement).
key_idYesNew encryption key id (3-32 chars, alnum/underscore start, then alnum/./_/-). CALLER-CHOSEN — PBS does not generate it.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the creation.
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?

Discloses mutation, risk medium, secret contract (key not written to audit), schema quirk (returns null), confirm behavior, return format, and config requirement. With no annotations, this fully compensates.

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?

Front-loaded with 'MUTATION: create'. Every sentence is purposeful, no fluff. Well-structured for quick parsing.

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?

Covers purpose, risk, secret handling, return behavior, and config needs. References sibling tool for follow-up. Adequate for an agent to invoke correctly.

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%, baseline 3. Description adds value by noting key is 'if given' kept secret, key_id is caller-chosen, and confirm default. Provides context beyond 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?

Clearly states 'create a PBS client encryption key' with specific verb and resource. Distinguishes from tape-encryption-keys plane, ensuring correct tool selection among siblings.

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?

Provides context on confirm (dry-run vs execute) and notes differences from tape keys. Lacks explicit when-not usage but implies alternatives via reference to pbs_encryption_key_list and tape plane.

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