Skip to main content
Glama
initMAX

Zabbix MCP Server

maintenance_get

Read-only

Retrieve maintenance periods to identify scheduled downtime windows that suppress problem notifications and optionally pause data collection for hosts or host groups.

Instructions

Retrieve maintenance periods. Maintenance windows suppress problem notifications and optionally pause data collection for specified hosts or host groups during scheduled downtime (e.g., patching windows).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return.
filterNoReturn only results whose properties exactly match the given values (a single value or a list of values per key). Example: {"status": 0} or {"status": [0, 1]}. Keys: active_since, active_till, maintenance_type, maintenanceid, name, tags_evaltype. Text properties cannot be filtered; use 'search' for them.
outputNoProperties of the maintenance object to return. Pass 'extend' for all, 'count' for the number of matches only, or a comma-separated list of property names. Default when omitted: maintenanceid, name, active_since, active_till. Properties: active_since, active_till, description, maintenance_type, maintenanceid, name, tags_evaltype.
searchNoReturn results whose string properties contain the given pattern (case-insensitive; '*' is a wildcard when searchWildcardsEnabled is true). Example: {"name": "web"}. Keys: description, name.
serverNoTarget Zabbix server. Available: default. Defaults to 'default' if omitted.
hostidsNoReturn only maintenance periods that affect the given hosts.
groupidsNoReturn only maintenance periods that affect the given host groups.
raw_jsonNoStrips the security disclaimer preamble from the response so it is pure JSON. Default: false. Requires the bearer token to have 'allow_raw_json' explicitly enabled by an operator in the admin portal - tokens without that policy receive a PolicyError instead. WARNING: setting true bypasses the prompt-injection mitigation marker that wraps untrusted Zabbix data (host names, item descriptions, problem text). LLM clients (Claude, GPT, Cursor, ...) should leave this false; only programmatic non-LLM consumers (Python scripts, n8n workflows that json.loads the result) should set true.
sortfieldNoSort by one or more of: maintenanceid, name, maintenance_type, active_since, active_till (comma-separated for several; pair with 'sortorder'). No other property is sortable.
sortorderNoSort order: 'ASC' (ascending) or 'DESC' (descending).
countOutputNoReturn the count of matching results instead of the actual data.
searchByAnyNoIf true, return results matching ANY search field (OR). Default is ALL fields (AND).
extra_paramsNoOther native maintenance.get parameters, merged into the request as-is. Sub-object selects (value 'extend', 'count' or a list of property names): selectGroups (removed in 7.2), selectHostGroups (6.2+), selectHosts, selectTags, selectTimeperiods. Any other key is refused here, because Zabbix would silently ignore it. For a parameter you are sure exists on your release but is not listed, use zabbix_raw_api_call.
maintenanceidsNoReturn only maintenance periods with the given IDs.
searchWildcardsEnabledNoIf true, enable * and ? wildcards in search patterns.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.41.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds domain semantics about what maintenance windows do, but says nothing about pagination, result volume, the security disclaimer wrapper, or the raw_json policy caveat that the schema documents. Useful context, but modest beyond the annotations.

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 sentences, zero filler, with the core action front-loaded before the domain explanation. Nothing to trim.

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 read-only listing tool with a full output schema, rich 100%-covered input schema, and clear annotations, the description is sufficient to call it correctly. It is slightly thin on when-to-use and pagination behavior, but nothing essential is missing.

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% across all 15 parameters, each with detailed documentation (filter keys, sortable fields, raw_json policy, extra_params sub-selects). The description adds no parameter guidance at all, 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 ('Retrieve maintenance periods') and adds a definition of what maintenance windows are, so the domain is unambiguous. It does not, however, differentiate itself from any alternative tool or note that it is the only maintenance-listing sibling, so it stops just 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 Guidelines2/5

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

The description explains what maintenance periods do in Zabbix (suppress notifications, pause data collection) but never says when an agent should call this tool versus alternatives, nor any prerequisite or exclusion. Usage is only implied by the verb 'Retrieve'.

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