Skip to main content
Glama

pbs_remote_create

Creates a remote PBS sync-source to enable backup synchronization between Proxmox servers. Dry-run by default; set confirm=True to apply.

Instructions

MUTATION (MEDIUM): create a PBS remote sync-source. Dry-run by default.

PRIVATE PASSWORD REDACTION: 'password' is a remote user credential. It is UNCONDITIONALLY redacted from the server-side plan, change, current state, detail, and audit ledger. Only {"password":"[redacted]"} is recorded on those surfaces. L02 NOTE: the MCP tool-call itself is a structured JSON object in which 'password' appears as a plain parameter — it is visible in the LLM's output token stream and in any MCP client log. This is an MCP-protocol property; server-side redaction protects the ledger only. The TLS cert 'fingerprint' is PUBLIC data — it is NOT redacted.

No rollback primitive — revert by deleting the remote (pbs_remote_delete). confirm=True to execute.

POST /config/remote Smoke-confirm: auth-id vs authid param name; port param name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostYesHostname or IP address of the remote PBS server.
nameYesName for the new PBS remote sync-source.
portNoTCP port of the remote PBS API; defaults to the standard PBS port if omitted.
auth_idYesPBS auth ID (user@realm or api-token) used to authenticate to the remote.
commentNoFree-text comment/description for the remote.
confirmNoSet True to execute; False (default) only returns the dry-run plan.
passwordYesPassword or API token secret for auth_id; redacted from all plans/logs/ledger.
fingerprintNoTLS cert fingerprint of the remote PBS server (public data, not redacted).
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?

Thoroughly describes mutation behavior, password redaction details, visibility in LLM output, and no rollback. No annotations exist, so the description carries full burden and excels.

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?

Well-structured with sections, but somewhat long. Front-loaded with purpose and security notes. Could be slightly more concise but still effective.

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 9 parameters, full schema coverage, and an output schema, the description covers mutation, security, dry-run, and revert. No gaps for the agent.

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. The description adds value by explaining the confirm parameter's role in dry-run behavior and password redaction, plus a note about parameter naming.

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 that creates a PBS remote sync-source, with a dry-run default. It distinguishes from siblings like pbs_remote_delete and pbs_remote_update.

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?

Explicitly mentions dry-run by default, confirm=True to execute, and no rollback primitive with the alternative to delete via pbs_remote_delete.

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