Skip to main content
Glama

pbs_tape_pool_update

Update a PBS tape media pool's allocation, retention, encryption, comment, or template. Dry-run by default; confirm to apply changes that affect future backup jobs.

Instructions

MUTATION: update a PBS tape media pool.

RISK_MEDIUM: changes allocation/retention policy and/or the encryption-key association — future tape-backup jobs writing into this pool target/reuse tapes under the new policy on their next run. NO digest/optimistic-lock param exists on this endpoint at all (schema- verified — see module docstring). Dry-run by default (captures current config into the PLAN); confirm=True executes (PUT /config/media-pool/{name}, synchronous — PBS returns null) and returns {"status": "ok", "result": None}. No snapshot primitive; re-apply the captured config to revert. Needs PROXIMO_PBS_* config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the existing media pool to update.
deleteNoProperty names to clear: any of allocation/retention/template/encrypt/comment.
commentNoNew comment (no control characters, <=128 chars).
confirmNoFalse (default) returns a dry-run PLAN only; True executes the update.
encryptNoNew tape encryption key fingerprint association.
templateNoNew media set naming template.
retentionNoNew retention policy: 'overwrite', 'keep', or a time span.
allocationNoNew allocation policy: 'continue', 'always', or a calendar event.
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?

With no annotations provided, the description fully covers behavioral aspects: mutation side effects on future jobs, no digest/lock, dry-run default, synchronous execution, null return, and revert method via captured config.

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?

The description is front-loaded with the mutation label and risk level, and each sentence contributes useful information without redundancy.

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 side effects, dry-run behavior, revert strategy, and config requirements. Output schema exists so return values need not be described. Adequate for a 9-parameter 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%, so baseline is 3. The description adds minimal value beyond the schema, only mentioning allocation/retention/encrypt parameters indirectly in risk context.

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 to update a PBS tape media pool, distinguishing it from sibling tools like create, delete, get, and list. The verb and resource are explicit.

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/confirm pattern and mentions the need for PROXIMO_PBS_* config. However, it does not explicitly state when to use this tool vs. sibling tools like create or delete.

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