Monitoring AIops

zabbix_create_maintenance

Destructive

Create a time-boxed Zabbix maintenance window for selected hosts or groups to suppress alerts during planned work; specify a duration in minutes.

Instructions

[WRITE][risk=medium] Create a time-boxed Zabbix maintenance window.

Requires minutes > 0 (never open-ended) and at least one host or group id. Reversible: the undo deletes exactly the maintenance id this call created.

Args: name: Maintenance window name shown in Zabbix. minutes: Window length in minutes (must be > 0). host_ids: Host ids to cover (from zabbix_hosts). group_ids: Host-group ids to cover (from zabbix_hostgroups). target: Zabbix target name from config; omit for the default.

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>",
      "minutes": "<minutes>"
    },
    "name": "zabbix_create_maintenance"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`target`	No
`minutes`	Yes
`host_ids`	No
`group_ids`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.9.0Sep 5, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already flag this as a non-idempotent destructive write, and the description adds real value on top: a medium risk rating, the mandatory minutes>0 constraint, and the precise reversal path ('the undo deletes exactly the maintenance id this call created'). It does not discuss authentication/permission requirements or rate limits, so it is strong but not exhaustive.

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?

Front-loaded with the [WRITE][risk=medium] tag and the action, followed by constraints, reversibility, and a compact Args block. Every line is useful and nothing is padding.

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 5-param mutation tool with no output schema, the description covers prerequisites, reversibility, and parameter provenance, which is nearly everything an agent needs. It is silent on return payload and permission requirements, which are minor residual gaps.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries the full burden and does so: it documents all five params, tells the agent where ids come from (zabbix_hosts, zabbix_hostgroups), and explains the target default ('omit for the default'). This adds meaning the bare schema cannot.

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 opens with a specific verb and resource ('Create a time-boxed Zabbix maintenance window') and adds a scoping qualifier ('time-boxed') that separates it from an open-ended window or from the sibling zabbix_delete_maintenance / zabbix_maintenances tools. An agent can identify what this does without opening the 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 states clear preconditions for use: minutes must be > 0 (never open-ended) and at least one host or group id is required. It gives strong context for when the call is appropriate but never names an alternative tool or an explicit when-not-to-use case.

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