Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

Maintenance Get

maintenance_get
Read-onlyIdempotent

Retrieve Zabbix maintenance periods to inspect planned monitoring pauses, filter by hosts, groups, or IDs, and page through results or count matches.

Instructions

Get maintenance periods from Zabbix.

Maintenance windows define periods when monitoring is paused for planned upgrades, maintenance, or testing. Alerts are suppressed during maintenance periods.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return. Default is 100.
offsetNoNumber of matching records to skip. Use with 'limit' to page through results; check 'has_more' and 'total' in the response.
outputNoextend
hostidsNoList of host IDs to get maintenance for. An empty list matches none.
groupidsNoList of host group IDs to get maintenance for. An empty list matches none.
sortfieldNoField to sort by. A deterministic sort is required for paging to be consistent.maintenanceid
sortorderNoSort direction - 'ASC' or 'DESC'.ASC
count_outputNoIf true, returns only the count of matched objects as an integer.
maintenanceidsNoList of maintenance IDs to get. Omit to return all maintenance periods; an empty list matches none.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.7.1
    • changedInput schema / properties / groupids / description
      Previous value: -"List of host group IDs to get maintenance for."New value: +"List of host group IDs to get maintenance for. An empty list matches none."
    • changedInput schema / properties / hostids / description
      Previous value: -"List of host IDs to get maintenance for."New value: +"List of host IDs to get maintenance for. An empty list matches none."
    • changedInput schema / properties / maintenanceids / description
      Previous value: -"List of maintenance IDs to get. If empty, returns all maintenance periods."New value: +"List of maintenance IDs to get. Omit to return all maintenance periods; an empty list matches none."
  2. Changed5 schema fields changedv0.6.0
    • changedInput schema / properties / offset / description
      Previous value: -"Number of results to skip (for pagination). Requires sortfield to be set."New value: +"Number of matching records to skip. Use with 'limit' to page through results; check 'has_more' and 'total' in the response."
    • removedInput schema / properties / sortfield / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • changedInput schema / properties / sortfield / default
      Previous value: -nullNew value: +"maintenanceid"
    • changedInput schema / properties / sortfield / description
      Previous value: -"Field to sort by."New value: +"Field to sort by. A deterministic sort is required for paging to be consistent."
    • addedInput schema / properties / sortfield / type
      Added value: +"string"
  3. First observedv0.5.3

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful domain semantics — that alerts are suppressed during these windows — but says nothing about result size, paging behavior, or the count_only mode, which are the operationally relevant traits.

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?

Three short sentences, front-loaded with the action, then useful domain context. Slight redundancy between sentences two and three, but no filler.

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 present, well-covered parameters, and explicit read-only annotations, the description covers what remains needed. Only the routing question (why choose this over other getters) is left unanswered.

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 89%, with limit, offset, hostids, groupids, maintenanceids, sortfield, sortorder, and count_output all documented inline. The description contributes no additional parameter meaning, so the baseline 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 and resource ('Get maintenance periods from Zabbix') and clarifies what a maintenance window is. It does not explicitly contrast with maintenance_create/update/delete, but the naming makes the read-vs-write split unambiguous.

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

Usage Guidelines2/5

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

Explains what maintenance windows are conceptually, but gives no guidance on when an agent should call this versus siblings such as problem_get, host_get, or maintenance_create. No exclusions, no typical triggers for invoking it.

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