Skip to main content
Glama

pbs_notification_endpoint_create

Create a Proxmox Backup Server notification endpoint for gotify, sendmail, smtp, or webhook. Returns a plan preview by default; confirm to execute.

Instructions

MUTATION: create a PBS notification endpoint. ep_type = gotify|sendmail|smtp|webhook. options carries the endpoint-specific config. Additive, RISK_LOW. Dry-run by default (returns a PLAN — any secret in options is masked to "[redacted]" in the preview); confirm=True executes (POST .../endpoints/{type}, synchronous — PBS returns null, not a task) and returns {"status": "ok", "result": None}. To modify an existing endpoint use pbs_notification_endpoint_update. Needs PROXIMO_PBS_* config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesUnique name for the new notification endpoint (2-32 chars, alnum start).
commentNoOptional free-text comment stored with the endpoint.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the creation.
disableNoIf True, create the endpoint disabled.
ep_typeYesNotification endpoint type: 'gotify', 'sendmail', 'smtp', or 'webhook'.
optionsNoType-specific config fields, e.g. gotify: {'server':.., 'token':..}; sendmail: {'mailto':[..]}; smtp: {'server':.., 'port':.., 'mailto':[..]}; webhook: {'url':.., 'method':.., 'header':[..], 'secret':[..]}. Credential-shaped keys (token/password/secret/header) are redacted from the PLAN preview and the audit ledger, but ARE sent to PBS on confirm=True.
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 discloses the mutation nature, dry-run behavior, synchronous execution, return format (null on confirm), secret redaction in preview and audit, and config requirement. This is comprehensive and transparent.

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 paragraph but efficiently conveys all necessary information: purpose, behavior, parameters, and sibling tool reference. Every sentence adds value, and the structure is logical.

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 7 parameters and an output schema, the description covers the tool's behavior, return types, parameter nuances, and error/redaction behavior. It is complete for an agent to correctly invoke the 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 description coverage is 100%, so baseline is 3. The description adds value by explaining ep_type values, options structure per type, and the confirm parameter's effect on execution vs preview. It also notes redaction behavior for credentials.

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 explicitly states 'create a PBS notification endpoint,' clearly identifying the verb (create) and resource. It also distinguishes from the sibling tool pbs_notification_endpoint_update, making the purpose unambiguous.

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?

The description explains the dry-run default and confirm=True execution, notes that it is additive with RISK_LOW, and explicitly says to use pbs_notification_endpoint_update for modifications. This provides clear when-to-use and when-not-to-use guidance.

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