Skip to main content
Glama

pve_notification_endpoint_update

Update an existing Proxmox notification endpoint. Dry-run returns a plan; confirm executes changes.

Instructions

MUTATION: update a PVE notification endpoint. ep_type = gotify|smtp|sendmail|webhook. options carries the endpoint-specific fields to change (same shape as create). Dry-run by default — captures current config into the PLAN; confirm=True executes and returns {"status": "ok", "result": null} (no further payload). No snapshot primitive; re-apply the captured config to revert, or use pve_notification_endpoint_create to make a new one instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the existing notification endpoint to update
commentNoOptional free-text comment to set on the endpoint
confirmNoFalse (default) returns a dry-run PLAN only; True executes the update
ep_typeYesNotification endpoint type: 'gotify', 'smtp', 'sendmail', or 'webhook'
optionsNoEndpoint-specific fields to change, same shape as create
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 vs execution behavior, return payload shape, and the absence of a snapshot primitive. It also notes the options shape matches create, adding behavioral context beyond the schema.

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 concise with only three sentences, each carrying essential information. It is front-loaded with 'MUTATION:' and structured to cover purpose, parameters, and behavioral notes efficiently.

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's complexity (6 params, 2 required, output schema present), the description adequately covers the update workflow, dry-run, execution, and revert options, making it complete for an AI agent to use correctly.

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%, but the description adds value by clarifying ep_type enum values, explaining options shape matches create, and detailing confirm's dual behavior. This goes beyond the schema's basic 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 to update a PVE notification endpoint, listing supported endpoint types (gotify, smtp, sendmail, webhook). It distinguishes from sibling tools like pve_notification_endpoint_create by mentioning creation as an alternative, and from delete/list by implication.

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 explicitly explains the dry-run default behavior, how to execute with confirm=True, and provides guidance on reverting changes by re-applying the captured config or using create. This gives clear when-to-use and when-not-to-use context.

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