Skip to main content
Glama

pbs_tape_key_delete

Delete a PBS tape encryption key. Use dry-run to view metadata; confirm to permanently remove the key, making tapes encrypted with it unreadable.

Instructions

MUTATION: delete a PBS tape encryption key.

RISK_HIGH: TAPES ENCRYPTED WITH THIS KEY BECOME UNREADABLE WITHOUT IT — PBS's own description, verbatim: "you can no longer access tapes using this key." No undo unless the key material was separately exported/backed up outside PBS. Dry-run by default (captures current public metadata); confirm=True executes (DELETE /config/tape-encryption-keys/{fingerprint}, 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.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the deletion.
fingerprintYesFingerprint of the tape encryption key to delete.
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, description fully discloses mutation risk: 'TAPES ENCRYPTED WITH THIS KEY BECOME UNREADABLE.' Details dry-run behavior, synchronous execution, null return, and configuration dependency. Comprehensive and honest.

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?

Extremely concise: uses front-loaded label ('MUTATION'), bullet-like risk warning, clear explanation of default behavior and execution. Every sentence adds necessary 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?

Description covers risk, default dry-run, execution details, return format, and config requirement. Lacks mention of error cases or permissions, but overall provides sufficient context for safe use.

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%, so baseline 3. Description adds context for confirm (dry-run vs execution) but no extra detail for other parameters beyond 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?

Description clearly states 'MUTATION: delete a PBS tape encryption key.' The verb 'delete' and resource 'PBS tape encryption key' are explicit. It distinguishes from sibling tools like pbs_tape_key_create and pbs_tape_key_get.

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?

Explains dry-run default and confirm=True execution. Mentions need for PROXIMO_PBS_* config. Does not explicitly state when to avoid or compare with alternatives, but the deletion context is clear.

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