Skip to main content
Glama

pbs_tape_media_status_set

Set or clear a tape medium's manual status override to mark it as full, damaged, or retired. Dry-run by default to preview changes before applying.

Instructions

MUTATION: set (or clear) a tape medium's manual status override.

RISK_MEDIUM: changes whether PBS considers this medium available for future writes — reversible by calling this again. Dry-run by default (returns a PLAN); confirm=True executes (POST /tape/media/list/{uuid}/status) and returns {"status": "ok", "result": None}. Needs PROXIMO_PBS_* config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uuidYesMedia UUID.
statusNoNew status: 'full', 'damaged', or 'retired'. Omit to CLEAR the manual override (revert to PBS's internally-managed writable/unknown state). 'writable'/'unknown' are rejected — PBS manages those internally.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the status change.
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?

Discloses mutation, reversibility, risk level, dry-run behavior, and expected return values. No annotations provided, so description fully handles transparency.

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?

Description is concise with 5 sentences, each adding distinct value. No wasted words, but could be slightly more compact.

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 risk, reversibility, config requirements, return format, and parameter details. Output schema exists but description still provides necessary context.

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 clear meaning for 'status' (allowed values and omission behavior) and 'confirm' (dry-run vs execution).

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?

Clearly states the tool 'set (or clear) a tape medium's manual status override.' Verb+resource+scope are explicit. Distinguishes from sibling 'pbs_tape_media_status_get' which is read-only.

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?

Provides context: dry-run by default, confirm needed to execute. Does not explicitly state when not to use or list alternatives, but usage is implied for overriding tape status.

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