Skip to main content
Glama

pbs_encryption_key_toggle_archive

Toggle a PBS encryption key's archive flag to prevent it from encrypting new content. Review current state first and dry-run to avoid silent failures.

Instructions

MUTATION: toggle a PBS client encryption key's archive flag.

RISK_MEDIUM: archived keys can no longer encrypt NEW content (PBS's own stated consequence) — reversible by toggling again, but automation relying on continued encryption with this key can silently start failing until noticed. Check pbs_encryption_key_list first to know the CURRENT archived state (this toggle flips whatever it currently is). Dry-run by default (returns a PLAN); confirm=True executes (POST /config/encryption-keys/{id}, synchronous — PBS returns null) and returns {"status": "ok", "result": None}. Needs PROXIMO_PBS_* config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
digestNoOptimistic-lock: 64-char lowercase hex SHA-256 of the config PBS last returned.
key_idYesId of the encryption key to toggle.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the toggle.
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 nature, risk (MEDIUM), reversibility, effect on encryption (archived keys cannot encrypt new content), dry-run behavior, synchronous execution, and exact return format. With no annotations provided, description fully carries the transparency burden.

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?

Description is well-structured with key points front-loaded (MUTATION, RISK_MEDIUM, behavior). All sentences add value. Slight redundancy in explaining dry-run and confirm, but overall concise.

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 the mutation's dry-run and confirm behavior, return format, potential risk, and prerequisite to check current state. Mentions required configuration. Output schema exists but is not shown; description adequately supplements.

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 description coverage is 100% with individual parameter descriptions. The tool-level description adds context for confirm (dry-run vs execution) and overall behavior but does not significantly enhance parameter semantics beyond what schema already provides.

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 the tool toggles the archive flag of a PBS client encryption key. Uses specific verb 'toggle' and resource 'PBS client encryption key's archive flag'. Distinguishes from sibling pbs_encryption_key_list by recommending to check current state first.

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 clear context: dry-run by default, confirm=True executes, and suggests checking state with pbs_encryption_key_list beforehand. Does not explicitly state when not to use, but gives sufficient direction for proper use.

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