Skip to main content
Glama

Get notification matcher fields

proxmox_get_notification_matcher_fields
Read-only

List notification metadata fields and their known values to write accurate match_field rules for Proxmox notification matchers.

Instructions

List the metadata fields notifications carry (type, hostname, job-id...) and their known values, for writing match_field rules in proxmox_save_notification_matcher.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, closed-world discovery call, and the description adds what the call actually returns: field names plus the values each field can take. It doesn't say how large or how current that value set is, which is a minor gap for a discovery tool.

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?

One sentence, front-loaded with what is listed and finished with the downstream use. Every clause carries information and none of it is wasted.

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?

The tool takes no parameters and has no output schema, so the description bears most of the weight. It covers what the tool returns and why that helps. A brief note on response shape or value coverage would close the remaining gap.

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?

With zero parameters and 100% schema coverage, there is nothing for the description to explain about inputs. The baseline of 4 is appropriate.

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 states a specific verb and resource: it lists the metadata fields notifications carry (with examples: type, hostname, job-id) and their known values. That is clearly distinct from proxmox_get_notification_matcher, which retrieves a matcher, and the intent is unambiguous without opening the empty schema.

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?

It names the moment to call it: identifying the fields to use when writing match_field rules in proxmox_save_notification_matcher. That gives a concrete trigger, but it doesn't say when the call is unnecessary (for example, when the caller already knows the field names).

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