Skip to main content
Glama

pbs_tape_media_destroy

Permanently delete a tape medium from Proxmox Backup Server's database. Dry-run by default; confirm to execute destruction.

Instructions

MUTATION: COMPLETELY REMOVES a tape medium from PBS's database.

RISK_HIGH: permanent, no undo — PBS's own description, verbatim: "completely remove from database". THE HTTP VERB IS GET, BUT THE EFFECT IS DESTRUCTIVE — the verb is not the safety signal here; this tool is PLAN-gated and confirm-gated exactly like every POST/PUT/DELETE mutation on this server. Dry-run by default (returns a PLAN, and the dry-run path never reaches the PBS API even though the real call is a GET); confirm=True executes (GET /tape/media/destroy) and returns {"status": "ok", "result": None}. Needs PROXIMO_PBS_* config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uuidNoMedia UUID identifying which medium to destroy. At least one of label_text/uuid is required.
forceNoForce removal even if this media is used in a media set.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the destroy.
label_textNoMedia label/barcode identifying which medium to destroy (2-32 chars). At least one of label_text/uuid is 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?

With no annotations, the description fully discloses the tool's behavior: permanent removal, GET verb with destructive effect, dry-run by default requiring confirm=True, and the need for PROXIMO_PBS_* configuration. It also describes the return 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 and front-loaded with the critical information ('MUTATION: COMPLETELY REMOVES'). It is detailed but concise, though some repetition about the HTTP verb could be trimmed.

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 destructive nature, 5 parameters, and no annotations, the description provides comprehensive context: destructive effect, safety mechanism, required configuration, return values, and parameter dependencies.

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?

The input schema has 100% description coverage, so the baseline is 3. The description reinforces the dry-run/confirm behavior and the config dependency but does not add significant new meaning beyond the 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?

The description explicitly states the action: 'COMPLETELY REMOVES a tape medium from PBS's database.' It uses a specific verb and resource, and clearly distinguishes this tool from siblings by highlighting its destructive nature.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains the destructive effect and the dry-run/confirm safety mechanism, but does not explicitly mention when to use this tool versus alternative tape media tools (e.g., pbs_tape_media_move). It provides context on the safety gate but lacks explicit exclusions or alternative recommendations.

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