Skip to main content
Glama
john-broadway

Proximo

by john-broadway
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

pbs_namespace_move

Move a backup namespace tree to a new parent within the same datastore. Dry-run by default; confirm to execute, with source deletion and potential breaking of references.

Instructions

MUTATION: move a backup namespace INCLUDING ALL CHILD NAMESPACES AND GROUPS to a new location within the same datastore.

RISK_HIGH — the widest-blast-radius non-deleting mutation on this plane: the whole tree relocates (max_depth defaults to full recursion upstream), the SOURCE tree is then REMOVED (delete_source defaults TRUE upstream), and every job (sync/prune/verify/tape), ACL path, and pull/push target referencing the old namespace path breaks or silently matches nothing afterward. Data survives at the target. Dry-run by default (the PLAN discloses every where-data-lands param including both upstream defaults); confirm=True executes (POST /admin/datastore/{store}/move-namespace, async — UPID; a null return records "ok"). No single-call undo. Needs PROXIMO_PBS_* config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nsYesSOURCE namespace to move. Must be non-empty — the root namespace cannot be relocated.
storeYesPBS datastore name (source and target — same datastore).
confirmNoFalse (default) returns a dry-run PLAN only; True executes the move.
max_depthNoRecursion depth 0-7. Upstream default 7 = FULL recursion — omitting it moves EVERYTHING under ns.
target_nsYesTARGET parent namespace. Empty string = move into the root namespace.
merge_groupsNoUpstream default TRUE: same-name groups already in the target get the moved snapshots merged in. False = fail on conflict.
delete_sourceNoUpstream default TRUE: the source namespace tree is REMOVED after the move. False = keep the (now-empty) source tree.
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

Tool Definition Quality

A4.9/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. It extensively discloses behavioral traits: mutation, high risk, destructive nature (delete_source defaults true), recursion up to 7 levels, async execution, dry-run vs confirm, and that data survives at target but old paths break.

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 dense and front-loaded with key information (MUTATION, RISK_HIGH, dry-run). However, it is somewhat long and could be slightly more concise, but each sentence earns its place.

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, mutations, async, no single-call undo), the description is comprehensive. It explains return types (PLAN, UPID, null), side effects, and prerequisites. Output schema exists but description still covers expected behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds significant meaning beyond schema: explains that ns must be non-empty, target_ns empty means root, max_depth default is full recursion, delete_source default is true, merge_groups default is true, and confirm toggles dry-run vs execution. Also explains proximo_target for multi-target config.

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 move a backup namespace including all child namespaces and groups within the same datastore. It differentiates from other namespace operations by emphasizing the move and relocation of entire subtrees.

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?

Provides explicit guidance: when to use (move namespace), warns of high risk and blast radius, recommends dry-run mode, and explains defaults like max_depth and delete_source. It clarifies that no single-call undo exists and config requirements.

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