Skip to main content
Glama

pbs_tape_drive_label_media

Write a new label to a tape drive's mounted media and optionally assign it to a media pool. Dry-run returns a plan; set confirm=True to execute. High risk: prior content becomes orphaned.

Instructions

MUTATION: write a NEW label to a drive's mounted media.

RISK_HIGH: writing a new label makes any PRIOR content on the tape ORPHANED/unaddressable through normal PBS tooling — rated the same tier as pbs_tape_drive_format even though raw bytes aren't erased. UNLIKE format-media, this op has NO built-in check that the tape is actually empty — PBS's only guidance is a prose note ("the media need to be empty"), never enforced. Call pbs_tape_drive_read_label first if unsure what's mounted. Dry-run by default (returns a PLAN); confirm=True executes (POST /tape/drive/{drive}/label-media) and returns {"status": "submitted", "result": ""}. No undo. Needs PROXIMO_PBS_* config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
poolNoMedia pool to assign the newly-labeled media to. Omit to assign it to the free-media pool.
driveYesDrive identifier.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the label write.
label_textYesThe NEW label text to write (2-32 chars, alnum/underscore start, then alnum/./_/-).
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, so description carries full burden. Discloses irreversible effect (prior content orphaned), risk level comparable to format, that PBS does not enforce empty check, and that there is no undo. Dry-run behavior and response format are also described.

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?

Description is concise, well-structured with clear labels (MUTATION, RISK_HIGH), and front-loads the core action and risk. Every sentence adds value without 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?

Complete for a complex, destructive tool. Covers action, risk, prerequisites, dry-run safety, execution mode, response format, and mentions undo not possible. No gaps given the context.

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 covers all parameters with descriptions, so baseline is 3. Description adds context about dry-run and confirm usage but does not significantly go beyond schema details.

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 clearly states it is a mutation that writes a new label to a drive's mounted media. It differentiates itself from siblings like pbs_tape_drive_format and pbs_tape_drive_read_label by explicitly comparing risks and prerequisites.

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

Usage Guidelines5/5

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

Provides explicit guidance: call pbs_tape_drive_read_label first if unsure, notes that dry-run is default and confirm=True executes, and contrasts with format-media regarding empty check. Tells agent when to use and when not.

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