Skip to main content
Glama

pdm_pbs_snapshots_list

List backup snapshots from a Proxmox Backup Server datastore via PDM without state changes. Optionally filter by namespace to find specific snapshots.

Instructions

READ-ONLY: list backup snapshots in one datastore on a PDM-registered PBS remote, proxied through PDM.

No state change. Returns a list of snapshot dicts (empty list if the datastore has none); live-verified (PDM 1.1 -> PBS 4.2). ns optionally filters by namespace. To query PBS directly without PDM, use pbs_snapshots_list. Needs PROXIMO_PDM_* config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nsNoOptional PBS namespace filter; omit to use the default namespace.
remoteYesPDM-registered PBS remote name, from pdm_remotes_list.
datastoreYesPBS datastore name on the remote to list snapshots from.
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, the description fully covers behavior: read-only, no state change, live-verified, returns list of snapshot dicts or empty list. No contradictions.

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?

Very concise with essential information front-loaded. Every sentence serves a purpose: purpose, safety, output, alternative, config. No redundancy.

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 output schema exists, the description covers all necessary context: purpose, usage, behavior, config requirements, and alternative tool. Complete for a list operation.

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 the description adds minimal value beyond what's in the schema. It mentions ns filtering but that is already in schema. The description does add context like 'live-verified' but that is not parameter-specific.

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 lists backup snapshots in a datastore on a PDM-registered PBS remote, proxied through PDM. It distinguishes from sibling pbs_snapshots_list by naming the alternative for direct access.

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 when-to-use (proxy through PDM) and when-not-to-use (direct PBS access via pbs_snapshots_list). Also mentions config requirements (PROXIMO_PDM_*).

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