Skip to main content
Glama

pbs_tape_drive_create

Create a Proxmox Backup Server tape drive configuration. Specify the drive name and SCSI device path; dry-run by default to preview changes before execution.

Instructions

MUTATION: create a PBS tape drive config.

RISK_MEDIUM: maps 'name' onto real host hardware at 'path' — a wrong path means a future tape job silently targets the wrong physical drive. Dry-run by default (returns a PLAN); confirm=True executes (POST /config/drive, synchronous — PBS returns null) and returns {"status": "ok", "result": None}. Needs PROXIMO_PBS_* config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesNew drive identifier (3-32 chars, alnum/underscore start, then alnum/./_/-).
pathYesPath to the LTO SCSI-generic tape device, e.g. '/dev/sg0'.
changerNoOptional tape changer identifier this drive is loaded by.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the creation.
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.
changer_drivenumNoOptional changer drive slot number (0-255, default 0; only meaningful with 'changer' set).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. It discloses mutation nature, dry-run vs confirm behavior, synchronous execution, risk of wrong path, and response format. Missing details on idempotency or duplicate handling, but otherwise transparent.

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?

Three sentences packed with info. Uses helpful tags like 'MUTATION:', 'RISK_MEDIUM:'. Could be slightly more structured, but overall concise and efficient.

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 purpose, risk, behavior, prerequisite. Output schema exists so return values not needed. Missing error handling or duplicate check, but adequate for a create tool.

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 coverage is 100% with good parameter descriptions. The description adds context: 'maps name onto real host hardware at path', dry-run vs confirm, and prerequisite. Adds value but does not drastically improve beyond 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 'MUTATION: create a PBS tape drive config', specifying the verb 'create' and resource 'PBS tape drive config'. It distinguishes from sibling tools like pbs_tape_drive_delete, pbs_tape_drive_get, etc.

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?

Describes dry-run default behavior (returns PLAN) and confirm=True execution. Mentions prerequisite 'Needs PROXIMO_PBS_* config.' Also highlights risk of wrong path. Does not explicitly state when to use vs alternatives, but purpose 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