Skip to main content
Glama

pbs_snapshot_protected_set

Set or clear the protected flag on a PBS snapshot to shield it from pruning and garbage collection (low risk) or to allow auto-deletion (high risk). Dry-run by default; confirm to execute.

Instructions

MUTATION: set or clear the protected flag on a PBS snapshot. RISK IS CONDITIONAL:

protected=True → LOW: shields the snapshot from pruning and GC (protective). protected=False → HIGH: SILENTLY re-enables pruning/GC — this recovery point can now be auto-deleted by the next prune job or GC run. No undo once auto-deleted.

No PBS snapshot primitive for rollback. Dry-run by default. confirm=True to execute. To annotate rather than protect a snapshot use pbs_snapshot_notes_set; to delete it outright use pbs_snapshot_delete.

PUT /admin/datastore/{store}/protected Smoke-confirm: exact path + param names (backup-type, backup-id, backup-time, protected).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nsNoNamespace path the snapshot lives in; omit for the root namespace.
storeYesPBS datastore name.
confirmNoSet True to execute; False (default) only returns the dry-run plan.
backup_idYesBackup group ID (e.g. VMID/CTID or host name).
protectedYesTrue shields the snapshot from pruning/GC (LOW); False allows auto-deletion (HIGH).
backup_timeYesSnapshot timestamp as a Unix epoch integer, identifying the exact backup run.
backup_typeYesBackup type of the snapshot: 'vm', 'ct', or 'host'.
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 discloses behavioral traits: it describes the conditional risk (LOW for protected=True, HIGH for protected=False), highlights the irreversible auto-deletion risk, notes the lack of rollback, and explains the dry-run default. This exceeds expectations for transparency.

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 concise and well-structured, using clear labels (MUTATION, RISK IS CONDITIONAL, Smoke-confirm) and bullet-like formatting. Every sentence adds necessary information without unnecessary repetition or fluff.

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 tool's complexity (8 parameters, mutation with conditional risk, dry-run), the description covers all essential aspects: purpose, risk, alternatives, execution flow, and endpoint. With an output schema present, the lack of return value description is acceptable. The description is complete for an agent to use correctly.

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?

While the schema has 100% coverage and describes all parameters, the description adds value by explaining the risk associated with the 'protected' parameter and the dry-run behavior tied to 'confirm'. It also mentions the endpoint path and parameter name verification, providing useful context beyond the 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 tool sets or clears the protected flag on a PBS snapshot. It distinguishes from related tools like pbs_snapshot_notes_set and pbs_snapshot_delete, and includes the HTTP endpoint for clarity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly explains when to use the tool, including the risk levels for each boolean value. It provides alternatives for similar actions and mentions the dry-run behavior and confirmation requirement, giving clear usage guidance.

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