Skip to main content
Glama

List notification matchers

proxmox_list_notification_matchers
Read-only

Lists Proxmox notification matchers so you can inspect rules that route alerts by severity, metadata, or calendar time to targets.

Instructions

List notification matchers: rules that route notifications (by severity, metadata fields such as type/hostname/job-id, and calendar time) to targets.

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_matchers"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNo
searchNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and idempotentHint=false, so the safety profile is covered by structured data. The description's added value is conceptual — explaining the matcher rule model — but it says nothing about result size, ordering, or how the two query parameters change the response. Nothing here contradicts the annotations.

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?

One front-loaded sentence with the resource stated first and elaboration after the colon, so the agent gets the core fact immediately. The parenthetical is dense but earns part of its space by defining matcher semantics. No filler or repetition.

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

Completeness2/5

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

For a simple list tool this covers the concept but not the mechanics: with zero schema coverage on two parameters and no output schema, the description is the only place parameter behavior could be explained, and it is silent. An agent still cannot tell what 'fields' or 'search' do, so the definition is not sufficient to invoke the tool confidently with arguments.

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

Parameters2/5

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

Schema description coverage is 0%, so both parameters ('fields' and 'search') carry no documented meaning anywhere. The description does not mention either parameter, leaving an agent to guess whether 'fields' selects returned columns or filters by matcher metadata, and whether 'search' is a substring or a structured expression. The parenthetical about type/hostname/job-id hints at matcher metadata but is never tied to the 'fields' parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (List) and resource (notification matchers), then goes further than the title by defining what a matcher actually is — a routing rule keyed on severity, metadata fields, and calendar time. An agent can tell this is a collection-read within the notification subsystem. It stops short of naming proxmox_get_notification_matcher or proxmox_list_notification_targets as the single-item/target counterparts, so the sibling distinction is left implicit.

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

Usage Guidelines2/5

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

The description contains no when-to-use, when-not-to-use, or alternative-selection guidance. It never says to call proxmox_get_notification_matcher when a single matcher's detail is wanted, nor does it distinguish this from proxmox_list_notification_targets. The only cue is the verb 'List', which is implied usage rather than stated guidance.

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