Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

Maintenance Update

maintenance_update
Destructive

Modify an existing Zabbix maintenance window by updating its name, start/end times, time periods, or description while leaving unspecified fields unchanged.

Instructions

Update an existing maintenance period in Zabbix.

Modifies properties of an existing maintenance window. You can change the name, start time, end time, time periods, or description. Only specify the fields you want to change.

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": {
      "maintenanceid": "<maintenanceid>"
    },
    "name": "maintenance_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew maintenance name.
active_tillNoNew end time (Unix timestamp).
descriptionNoNew description.
timeperiodsNoReplaces all of the maintenance's time periods, e.g. [{'timeperiod_type': 0, 'start_date': 1735689600, 'period': 3600}]. Omit to keep them; a one-off period created for the old window is moved along with it.
active_sinceNoNew start time (Unix timestamp).
maintenanceidYesID of the maintenance to update.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.7.1
    • addedInput schema / properties / timeperiods
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "additionalProperties": true,
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Replaces all of the maintenance's time periods, e.g. [{'timeperiod_type': 0, 'start_date': 1735689600, 'period': 3600}]. Omit to keep them; a one-off period created for the old window is moved along with it."
      +}
  2. First observedv0.5.3

TDQS

B3.4/5.0
Behavior3/5

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

Annotations declare destructiveHint=true and idempotentHint=false, so the description should warn about the destructive behavior; instead it merely says time periods "can be changed" without disclosing (as the schema does) that the array replaces all existing periods. The partial-update sentence adds genuine value beyond annotations, but the destructive/idempotency implications are left undisclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core action is front-loaded in the first sentence and the operative guidance is short and actionable. The second sentence ("Modifies properties of an existing maintenance window") largely restates the first, so a small amount of text does not fully earn its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained. But for a destructive, non-idempotent mutation the description omits the risk context an agent needs — that passing timeperiods wipes and replaces all periods, and that maintenanceid must reference an existing window.

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%, so the baseline is 3. The description enumerates the mutable fields (name, start time, end time, time periods, description) consistent with the schema, but adds no format, timestamp-unit, or nesting semantics beyond what the schema already documents.

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 and resource ("Update an existing maintenance period in Zabbix") and the word "existing" implicitly separates it from maintenance_create/maintenance_delete. It stops short of naming those siblings or the maintenance_get read path, so differentiation is inferred rather than explicit.

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?

"Only specify the fields you want to change" gives useful partial-update guidance, which is real usage context. However there is no statement of when to use this versus maintenance_create, no prerequisites (permissions, whether the window must be active), and no exclusions.

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