Skip to main content
Glama
john-broadway

Proximo

by john-broadway
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

pbs_remote_update

Update an existing Proxmox Backup Server remote configuration. Dry-run by default; set confirm=True to apply changes.

Instructions

MUTATION (MEDIUM): update an existing PBS remote. Dry-run by default.

CAPTURE: reads current (non-secret) config before planning; on failure plan is marked incomplete. PRIVATE PASSWORD REDACTION: if 'password' is provided it is UNCONDITIONALLY redacted from the server-side plan, change, current state, detail, and audit ledger. L02 NOTE: the MCP tool-call itself is a structured JSON object in which 'password' appears as a plain parameter — visible in the LLM's output token stream and any MCP client log. This is an MCP-protocol property; server-side redaction protects the ledger only. The TLS cert 'fingerprint' is PUBLIC and appears in plans/logs for audit. No rollback primitive — revert by re-applying captured config. confirm=True to execute. Use pbs_remote_get to inspect current config first.

PUT /config/remote/{name} Smoke-confirm: auth-id param name; whether partial PUT is accepted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostNoNew hostname or IP address of the remote PBS server.
nameYesPBS remote sync-source name to update.
portNoNew TCP port of the remote PBS API.
auth_idNoNew PBS auth ID (user@realm or api-token) used to authenticate to the remote.
commentNoNew free-text comment/description for the remote.
confirmNoSet True to execute; False (default) only returns the dry-run plan.
passwordNoNew password or API token secret; redacted from plans/logs/ledger.
fingerprintNoNew TLS 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

Tool Definition Quality

A4.8/5.0
Behavior5/5

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

Despite no annotations, the description thoroughly discloses behavior: dry-run default, captures current config before planning, password redaction from logs/ledger, MCP protocol visibility note, fingerprint as public, and 'Smoke-confirm' about auth-id and partial PUT.

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 long but well-structured with clear sections (MUTATION, CAPTURE, etc.) and front-loaded key info. Some parts like 'Smoke-confirm' are cryptic but overall efficient.

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, description needn't explain return values. It covers all critical aspects: safety, behavior, prerequisites, and notes on privacy. Complete for a complex mutation tool.

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%, so baseline is 3. Description adds value: password 'UNCONDITIONALLY redacted', fingerprint 'PUBLIC', confirm=True for execution, and context about auth-id and partial PUT. Slightly above baseline.

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 update an existing PBS remote, distinguishing it from siblings like pbs_remote_get (inspect current config) and pbs_remote_create (create new). It specifies the verb 'update' and the resource 'PBS remote'.

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?

Explicit guidance: 'Use pbs_remote_get to inspect current config first.' Also states dry-run by default and confirm=True to execute. Provides context on when to use and alternatives (no rollback primitive).

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