Skip to main content
Glama

Get notification matcher

proxmox_get_notification_matcher
Read-only

Retrieve a Proxmox notification matcher's rules, targets, and digest to inspect its configuration and safely plan updates.

Instructions

Get one notification matcher's rules and targets (plus its digest for safe updates).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
nameYesMatcher name (see proxmox_list_notification_matchers)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the read-only and closed-world profile, so the description only needs to add context beyond that. It does: disclosing that the response includes a digest used for safe updates is a non-obvious concurrency trait that an agent would not get from the annotations or schema. It stops short of describing not-found behavior or required permissions.

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 the verb and resource, with the return payload and the digest caveat in a tight parenthetical. No filler and nothing redundant with the schema.

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 carries the burden of telling the agent what comes back, and it does so (rules, targets, digest). For a single-parameter read tool that is nearly sufficient; only failure behavior for an unknown matcher name is left unstated.

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 coverage is 100% and the single 'name' parameter is already documented in the schema with a pointer to proxmox_list_notification_matchers. The description adds no format, case-sensitivity, or lookup details beyond that, so the baseline of 3 applies.

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+resource ('Get one notification matcher') and scopes it to a single object, which cleanly separates it from the list-style sibling. It also names what comes back (rules, targets, digest). It does not explicitly name an alternative, but the singular-vs-list distinction is clear from the wording.

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

Usage Guidelines3/5

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

The parenthetical 'for safe updates' implies the intended workflow (fetch the digest before mutating), which is useful implied guidance. There is no explicit when-to-use/when-not statement and no named alternative such as the fields or list tools, so the agent must infer the context.

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