Skip to main content
Glama

pve_notification_endpoint_delete

Delete a Proxmox VE notification endpoint by type and name. Performs a dry-run to capture the current configuration by default; set confirm=True to execute the deletion.

Instructions

MUTATION: delete a PVE notification endpoint. ep_type = gotify|smtp|sendmail|webhook. Dry-run by default — captures current config. confirm=True executes and returns {"status": "ok", "result": null} (no further payload). No UNDO primitive — matchers referencing this endpoint silently fail until it is re-created with pve_notification_endpoint_create.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the notification endpoint to delete
confirmNoFalse (default) returns a dry-run PLAN only; True executes the deletion
ep_typeYesNotification endpoint type: 'gotify', 'smtp', 'sendmail', or 'webhook'
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?

No annotations provided, so description carries full burden. Clearly labels as mutation, explains dry-run vs execution behavior, specifies response format for confirm=True, and discloses consequences (no undo, matcher failure). This exceeds typical transparency requirements.

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?

Three sentences, each purposeful. First sentence states purpose and valid types. Second covers dry-run and confirm. Third warns about consequences. No redundancy. Front-loaded with critical info.

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 output schema exists, description is sufficient. Explains return payload for confirm=True and mentions dry-run captures current config. Could mention prerequisites (endpoint must exist) but schema's required fields imply that. Overall, well-rounded for a delete 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 description adds value beyond schema by listing allowed ep_type values in a compact form and clarifying the confirm parameter's effect on return value. No additional details for name or proximo_target are needed.

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?

Starts with 'MUTATION: delete a PVE notification endpoint', clearly identifying the action and resource. Distinguishes from sibling tools like create/update/list by specifying delete. Also lists valid ep_type values, making the scope explicit.

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?

States dry-run default and confirm flag for execution, guiding safe usage. Warns about no UNDO and matchers silently failing, which helps the agent decide when to use this tool. However, it does not explicitly compare against alternatives like updating the endpoint instead of deleting.

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