Skip to main content
Glama

pve_notification_endpoint_create

Creates a Proxmox VE notification endpoint for types like Gotify, SMTP, sendmail, or webhook. Supports dry-run mode; confirm with 'confirm=True' to execute.

Instructions

MUTATION: create a PVE notification endpoint. ep_type = gotify|smtp|sendmail|webhook. Dry-run by default. confirm=True to execute. options carries the endpoint-specific config (sendmail: {"mailto-user":"root@pam"}; gotify: {"server":..,"token":..}; webhook: {"url":..}).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
commentNo
confirmNo
ep_typeYes
optionsNo
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
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses mutation, dry-run behavior, and provides examples of 'options' configuration. It does not cover auth needs or rate limits, but the information given is valuable and sufficient for safe use.

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 4 sentences, front-loads the purpose, and uses clear examples. No redundant or unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 6 parameters and an output schema, the description covers creation, dry-run, type options, and options examples. It doesn't describe the output schema (which is fine) or error conditions, but it is complete enough for effective use.

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 low (17%), but the description adds key meaning: lists allowed values for ep_type, explains confirm parameter for dry-run, and gives examples for options. It doesn't detail name or comment, but the added info compensates well.

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 creates a PVE notification endpoint and lists the specific endpoint types. It distinguishes from siblings like delete, list, and update by focusing on creation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description indicates when to use the tool (to create endpoints) and explains dry-run behavior and the need for confirm=True to execute. However, it doesn't explicitly exclude other contexts or mention scenarios where alternatives (e.g., update) are better suited.

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