Monitoring AIops

zabbix_maintenances

Read-only

Read Zabbix maintenance windows with their hosts, groups, and periods to track scheduled downtime and maintenance coverage.

Instructions

[READ] Zabbix maintenance windows with their hosts/groups and periods.

Args: target: Zabbix target name from config; omit for the default.

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": "zabbix_maintenances"
  }
}

Input Schema

Name	Required	Description	Default
`target`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.9.0Sep 5, 2026

TDQS

A3.7/5.0

Behavior3/5

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

readOnlyHint=true already establishes the safe-read profile, so the description only needs to add context. It does add the returned composition ('with their hosts/groups and periods'), but says nothing about pagination, time-range scoping, or empty results for a list 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?

Two tight lines: purpose first, then a single optional-argument note. Nothing is redundant or padded.

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?

For a one-optional-parameter read tool with no output schema, the description covers the resource, the returned structure, and the parameter semantics. Only the absence of filtering/pagination notes keeps it from being fully complete.

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 description coverage is 0%, so the schema alone gives no meaning for 'target'. The description compensates by explaining it is a Zabbix target name from config and that omitting it selects the default, which is exactly the information an agent needs.

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 (read/list, marked [READ]) and a specific resource (Zabbix maintenance windows), plus what it returns: hosts/groups and periods. It is distinguishable from the zabbix_create_maintenance and zabbix_delete_maintenance siblings, but it never names an alternative explicitly, so it falls short of the top band.

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?

Usage is only implied by the [READ] tag and the plural-resource name; there is no explicit guidance on when to call this versus zabbix_create_maintenance, zabbix_delete_maintenance, or zabbix_events. The 'omit for the default' note is the only operational guidance offered.

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