Skip to main content
Glama

pve_notification_endpoint_create

Create a notification endpoint for Proxmox VE (e.g., gotify, SMTP, sendmail, or webhook). Dry-run by default; set confirm=true to execute.

Instructions

MUTATION: create a PVE notification endpoint. ep_type = gotify|smtp|sendmail|webhook. options carries the endpoint-specific config (sendmail: {"mailto-user":"root@pam"}; gotify: {"server":..,"token":..}; webhook: {"url":..}). Additive, low risk. Dry-run by default (returns a PLAN); confirm=True executes and returns {"status": "ok", "result": null} (no further payload). To modify an existing endpoint instead use pve_notification_endpoint_update.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesUnique name for the new notification endpoint
commentNoOptional free-text comment stored with the endpoint
confirmNoFalse (default) returns a dry-run PLAN only; True executes the creation
ep_typeYesNotification endpoint type: 'gotify', 'smtp', 'sendmail', or 'webhook'
optionsNoEndpoint-specific config fields, e.g. sendmail: {'mailto-user':'root@pam'}; gotify: {'server':.., 'token':..}; webhook: {'url':..}
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?

Despite no annotations, the description fully discloses behavioral traits: mutation, low risk, additive, dry-run capability, and exact return formats for both dry-run and execution modes.

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?

The description is informative but slightly lengthy; however, every sentence contributes value. It is well-structured with clear purpose first.

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 6 parameters (2 required) and no annotations, the description covers purpose, endpoint types, options examples, dry-run behavior, return values, and sibling reference. Output schema exists but description already explains returns. Complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds concrete examples for 'options' per endpoint type (sendmail, gotify, webhook) and clarifies the confirm parameter's effect, enriching understanding beyond the schema.

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 create a PVE notification endpoint, lists allowed ep_type values, and explicitly distinguishes from the sibling tool pve_notification_endpoint_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?

Provides explicit guidance: dry-run by default (confirm=False returns a PLAN), confirm=True executes and returns a specific response, and directs to use pve_notification_endpoint_update for modifications. No ambiguity.

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