Skip to main content
Glama

pbs_tape_drive_format

Format a tape drive's media, with dry-run planning and optional label verification to prevent accidental destruction.

Instructions

MUTATION: format (ERASE) a drive's mounted media.

RISK_HIGH: DESTROYS ALL DATA on the mounted tape, no undo. If label_text is supplied, PBS cancels the format on a mismatch — real, but OPT-IN, protection. Omitting it formats whatever is loaded UNCONDITIONALLY. Dry-run by default (returns a PLAN); confirm=True executes (POST /tape/drive/{drive}/format-media) and returns {"status": "submitted", "result": ""}. Needs PROXIMO_PBS_* config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fastNoUse fast erase (PBS default: True if omitted).
driveYesDrive identifier.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the format.
label_textNoIf given, PBS cancels the format when the MOUNTED tape's own current label doesn't match this value — protects against formatting the wrong cartridge. Omit and PBS formats unconditionally.
load_barcodeNoIf given, PBS first loads the cartridge carrying this barcode from the changer, THEN formats it (implicit load-then-format).
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 exist, so description carries full burden. It discloses mutation, high risk, dry-run default, execution behavior, return format, label_text protection, and config requirement. Highly transparent.

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 and front-loaded with key warnings. Uses capital letters for emphasis. Every sentence provides necessary information without fluff.

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?

Covers main behavior, return types, safety mechanisms, and config requirement. Could mention prerequisites like tape must be loaded, but given output schema exists, this is sufficient.

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 explaining the critical parameters confirm (dry-run vs execute) and label_text (safety check), going beyond schema descriptions. Does not cover all parameters but leverages existing 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 clearly states the verb 'format (ERASE)' and the resource 'a drive's mounted media', distinguishing it from sibling tools like clean or label. The purpose is unmistakable.

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?

Explicitly explains dry-run vs execution behavior and the label_text safety mechanism. Does not explicitly state when not to use or name alternatives, but the destructive nature and context strongly imply usage boundaries.

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