Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

Maintenance Create

maintenance_create

Creates a Zabbix maintenance window that suppresses alerts during planned upgrades, patching, or system work to prevent false alarms.

Instructions

Create a new maintenance period in Zabbix.

Schedules a maintenance window when monitoring alerts are suppressed. Useful for planned upgrades, patching, or system maintenance without triggering false alarms.

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>",
      "active_since": "<active_since>",
      "active_till": "<active_till>"
    },
    "name": "maintenance_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesMaintenance name.
hostidsNoList of specific host IDs to apply maintenance to.
groupidsNoList of host group IDs to apply maintenance to. At least one of groupids or hostids is required.
active_tillYesEnd time (Unix timestamp).
descriptionNoOptional description explaining the maintenance purpose.
timeperiodsNoWhen maintenance actually runs, e.g. [{'timeperiod_type': 0, 'start_date': 1735689600, 'period': 3600}]. Required by Zabbix; if omitted, a single one-off period covering active_since to active_till is sent.
active_sinceYesStart time (Unix timestamp).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.0
    • changedInput schema / properties / timeperiods / description
      Previous value: -"Optional list of time period objects for recurring maintenance."New value: +"When maintenance actually runs, e.g. [{'timeperiod_type': 0, 'start_date': 1735689600, 'period': 3600}]. Required by Zabbix; if omitted, a single one-off period covering active_since to active_till is sent."
  2. First observedv0.5.3

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the mutating-but-non-destructive profile is covered structurally. The description's genuine addition is the effect semantics: alerts are suppressed during the window, which motivates creation. It does not mention overlap with existing maintenance, permission requirements, or that non-idempotent calls create duplicates, so a 3 is appropriate.

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?

Three short sentences, front-loaded with the action, then the semantic explanation, then use cases. No filler or restatement of the title.

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 an output schema, full parameter documentation, and annotations present, the description only needs to supply purpose and context, which it does. Minor gaps remain around target scoping (hosts vs. groups) and scheduling edge cases, but nothing blocks a correct call.

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 description coverage is 100%, including the subtle constraint that at least one of groupids/hostids is required and the timeperiods fallback behavior, so the schema does the heavy lifting and a 3 baseline applies. The description adds no parameter-level meaning of its own — no mention of target scoping or timestamp units.

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?

States a specific verb and resource ('Create a new maintenance period in Zabbix') and immediately explains what that object means ('Schedules a maintenance window when monitoring alerts are suppressed'). The verb distinguishes it cleanly from maintenance_get, maintenance_update, and maintenance_delete in the sibling list.

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?

Gives concrete when-to-use context — 'planned upgrades, patching, or system maintenance without triggering false alarms' — which tells the agent the operational scenario. It stops short of exclusions or naming alternatives (e.g. use maintenance_update to extend an existing window instead of creating a duplicate), so it is clear but not fully directive.

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