Skip to main content
Glama

pbs_namespace_delete

Delete a namespace from a PBS datastore. Dry-run by default; set confirm=True to execute. Use delete_groups=True to remove all backup groups inside the namespace (irreversible).

Instructions

MUTATION: delete a namespace from a PBS datastore. Dry-run by default — delete_groups=True is HIGH (it deletes all backup groups/snapshots inside the namespace, no undo). confirm=True to execute — returns {"status": "ok", "result": null}. Use pbs_namespaces_list to confirm it's empty first, or pbs_namespace_create to recreate an empty namespace afterward.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nsYesNamespace path to delete.
storeYesPBS datastore name.
confirmNoSet True to execute; False (default) only returns the dry-run plan.
delete_groupsNoIf True, deletes groups/snapshots in namespace (HIGH, no undo); else must be empty.
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?

No annotations are provided, so the description fully bears the responsibility. It details the dry-run default behavior, the irreversible nature of delete_groups=True, the execute flag (confirm), and the exact return format. This exceeds necessary disclosure.

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 a single, well-structured paragraph with no wasted words. It front-loads the action type and core behavior, then provides key details about flags and related tools.

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 has 5 parameters (2 required) and an output schema, the description covers the essential behavioral aspects, side effects, safe execution workflow, and references to sibling tools for completeness. No gaps remain.

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?

The input schema covers 100% of parameters, but the description adds crucial meaning: explaining that delete_groups=True 'deletes all backup groups/snapshots inside the namespace, no undo', and that confirm=True is needed to execute. This goes beyond the schema descriptions.

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: delete a namespace from a PBS datastore', explicitly distinguishing it from sibling tools like pbs_namespaces_list and pbs_namespace_create. The purpose is specific and unambiguous.

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 advises using pbs_namespaces_list to confirm emptiness before deletion, and pbs_namespace_create to recreate if needed. It also warns about the high risk of delete_groups=True without explicit alternatives to this tool itself, but provides good context on when to use safety checks.

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