Skip to main content
Glama

List notification targets

proxmox_list_notification_targets
Read-only

Lists Proxmox VE notification targets across sendmail, SMTP, Gotify, and webhook types, showing status, origin, and comments; optionally include redacted endpoint configuration.

Instructions

List all notification targets (endpoints of every type: sendmail, smtp, gotify, webhook) with type, disabled state, origin and comment. details=true adds each endpoint's configuration (secrets redacted). Matchers decide which notifications go to which target; see proxmox_list_notification_matchers.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "proxmox_list_notification_targets"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNo
searchNo
detailsNoInclude each endpoint's full configuration (one extra call per type)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description still adds real context: secrets are redacted in configuration output and details=true costs 'one extra call per type', which is important performance information not present in structured fields. Auth requirements and enumeration limits are not mentioned, keeping it below a 5.

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 carrying distinct information (scope/returned fields, the details flag and its cost, matcher cross-reference), with the scope front-loaded. No filler or restatement of the tool title.

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?

With no output schema, the description compensates by naming the returned fields and the redaction behavior, which is what an agent needs to interpret results. The remaining gap is the unexplained 'fields' and 'search' parameters and no mention of result-set size or pagination behavior.

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

Parameters3/5

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

Schema description coverage is only 33% — just 'details' is documented in the schema — and the description usefully extends that with the secrets-redaction and extra-call cost. However, 'fields' and 'search' receive no explanation in either the schema or the description, so half the parameter surface remains undefined.

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?

States a specific verb and resource ('List all notification targets'), enumerates the covered endpoint types (sendmail, smtp, gotify, webhook), and names the fields returned (type, disabled state, origin, comment). An agent can distinguish this from the singular get_notification_endpoint siblings by the 'all... every type' scope.

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?

Gives a concrete condition for toggling details=true (when the per-endpoint configuration is needed) and routes matcher-related questions to proxmox_list_notification_matchers. It does not state when NOT to use this tool (e.g. to fetch a single endpoint by name), so it stops short of full alternative routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools