Skip to main content
Glama

pbs_group_move

Move a backup group between namespaces within the same datastore. Use dry-run to plan, then confirm to execute the move.

Instructions

MUTATION: move a backup group to a different namespace within the same datastore.

RISK_MEDIUM — data-relocating, not destroying: sync/verify/prune jobs, ACL paths, and pull/push targets scoped to the OLD namespace silently stop seeing this group afterward. Dry-run by default (the PLAN discloses source ns, target ns, and the merge behavior including the upstream default); confirm=True executes (POST /admin/datastore/{store}/move-group, async — UPID; a null return records "ok") and tracks with pbs_tasks_list. Reverse with a second pbs_group_move. Needs PROXIMO_PBS_* config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nsNoSOURCE namespace; omit for the root namespace.
storeYesPBS datastore name (source and target — same datastore).
confirmNoFalse (default) returns a dry-run PLAN only; True executes the move.
backup_idYesBackup group ID to move.
target_nsNoTARGET namespace; omit for the root namespace.
backup_typeYesBackup type: vm, ct, or host.
merge_groupNoUpstream default TRUE: if the group already exists in the target namespace, merge snapshots into it (requires matching ownership and non-overlapping snapshot times). False = fail instead.
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 side effects (jobs stop seeing group), risk level (RISK_MEDIUM, data-relocating), dry-run behavior, async execution (UPID), reversibility, and config prerequisite. Exceptionally 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?

Front-loaded with action and risk, then logical flow: side effects, dry-run, confirm, reverse, config. Every sentence adds value, though slightly verbose with multiple clauses. No wasted text.

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?

Given 8 params and output schema exists, description covers operation, safety, side effects, execution model, reversibility, and prerequisites. Return values are handled by output schema. Could mention permissions but config requirement is noted.

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 meaning beyond schema by explaining confirm's effect (POST endpoint, async, UPID, null return), merge_group's default and merging behavior, and the impact of omitting ns/target_ns (root namespace).

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 verb (move), resource (backup group), and scope (different namespace, same datastore). Distinguishes from sibling tools like pbs_group_delete by specifying the move operation across namespaces.

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

Usage Guidelines3/5

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

Describes dry-run by default and confirm execution, mentions reversibility, but does not explicitly state when to use vs alternatives like pbs_namespace_move or other group operations. Usage is implied but not contrasted with siblings.

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