Skip to main content
Glama

pbs_tape_media_move

Update the location bookkeeping of a tape medium to a vault or offline. Dry-run returns a plan; confirm=true executes the change.

Instructions

MUTATION: change a tape medium's LOCATION bookkeeping (to a vault, or to offline).

RISK_MEDIUM: does not physically move anything — updates PBS's own tracking field. A scheduled job/inventory expecting this medium online in a changer fails to find it until the bookkeeping matches reality again. Dry-run by default (returns a PLAN); confirm=True executes (POST /tape/media/move) and returns {"status": "ok", "result": None}. Needs PROXIMO_PBS_* config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uuidNoMedia UUID identifying which medium to move. At least one of label_text/uuid is required.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the location change.
label_textNoMedia label/barcode identifying which medium to move. At least one of label_text/uuid is required.
vault_nameNoVault to move the medium's location to (3-32 chars). OMIT to set location to OFFLINE instead — not a no-op.
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?

Despite no annotations, the description fully discloses that it is a mutation, does not physically move anything, updates only PBS's tracking field, and warns that scheduled jobs expecting the medium online may fail. It also describes the dry-run/confirm flow and return values.

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?

The description is extremely concise, uses whitespace effectively, and front-loads the key action and risk. Every sentence adds value—no filler.

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 5 parameters, no required fields, and presence of an output schema, the description is complete: it explains the mutation behavior, dry-run vs execution, return values, prerequisites, and side effects. The output schema is not detailed, but the description covers what the tool returns.

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%, so baseline is 3. The description adds some context (e.g., dry-run default relates to confirm, omission of vault_name sets offline) but does not significantly extend the schema descriptions for individual parameters.

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 'change' and the resource 'tape medium's LOCATION bookkeeping' with scope 'to a vault, or to offline'. It distinguishes this from other pbs_tape_* tools by emphasizing it only updates bookkeeping, not physical movement.

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?

The description explains the dry-run default and confirm behavior, prerequisites (PROXIMO_PBS_* config), and risk implications. It implicitly tells when to use (to update location tracking) but does not explicitly contrast with alternatives like pbs_tape_media_destroy or pbs_tape_drive_load_media.

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