Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

maintenance_get

Read-only

Retrieve Zabbix maintenance periods to identify scheduled downtime windows, check which hosts or host groups are affected, and verify when problem notifications are suppressed or data collection is paused.

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

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 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 (a list 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. Parameters: groupCount, triggerids (8.0+). Switches (true turns one on, false is the same as leaving it out): groupCount. groupCount goes with output='count': the count is then split by the ID filters the method groups by (hostids, groupids ...), one row per ID with 'rowscount'; a single row without such a filter. Sub-object selects (value 'extend', 'count' or a list of property names): selectEventNames (8.0+), selectGroups (removed in 7.2), selectHostGroups (6.2+), selectHosts, selectTags, selectTimeperiods, selectTriggers (8.0+). 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv1.42.2
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / extra_params / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "propertyNames": {
      +      "enum": [
      +        "editable",
      +        "excludeSearch",
      +        "preservekeys",
      +        "startSearch",
      +        "groupCount",
      +        "triggerids",
      +        "selectEventNames",
      +        "selectGroups",
      +        "selectHostGroups",
      +        "selectHosts",
      +        "selectTags",
      +        "selectTimeperiods",
      +        "selectTriggers"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / extra_params / description
      Previous value: -"Other 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."New value: +"Other native maintenance.get parameters, merged into the request as-is. Parameters: groupCount, triggerids (8.0+). Switches (true turns one on, false is the same as leaving it out): groupCount. groupCount goes with output='count': the count is then split by the ID filters the method groups by (hostids, groupids ...), one row per ID with 'rowscount'; a single row without such a filter. Sub-object selects (value 'extend', 'count' or a list of property names): selectEventNames (8.0+), selectGroups (removed in 7.2), selectHostGroups (6.2+), selectHosts, selectTags, selectTimeperiods, selectTriggers (8.0+). 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."
    • changedInput schema / properties / filter / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "propertyNames": {
      +      "enum": [
      +        "active_since",
      +        "active_till",
      +        "maintenance_type",
      +        "maintenanceid",
      +        "name",
      +        "tags_evaltype"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / output / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "extend",
      +      "count"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "active_since",
      +        "active_till",
      +        "description",
      +        "maintenance_type",
      +        "maintenanceid",
      +        "name",
      +        "tags_evaltype"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / output / description
      Previous value: -"Properties 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."New value: +"Properties of the maintenance object to return. Pass 'extend' for all, 'count' for the number of matches only, or a 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."
    • changedInput schema / properties / search / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "propertyNames": {
      +      "enum": [
      +        "description",
      +        "name"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / sortfield / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "maintenanceid",
      +      "name",
      +      "maintenance_type",
      +      "active_since",
      +      "active_till"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "maintenanceid",
      +        "name",
      +        "maintenance_type",
      +        "active_since",
      +        "active_till"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / sortfield / description
      Previous value: -"Sort 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."New value: +"Sort by one or more of: maintenanceid, name, maintenance_type, active_since, active_till (a list for several; pair with 'sortorder'). No other property is sortable."
    • changedInput schema / properties / sortorder / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "ASC",
      +      "DESC"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "ASC",
      +        "DESC"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "result": {
      -      "title": "Result",
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "result"
      -  ],
      -  "title": "maintenance_getOutput",
      -  "type": "object"
      -}New value: +null
  2. First observedv1.41.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful domain semantics (maintenance suppresses problem notifications and can pause data collection), but says nothing about pagination, default returned fields, the count output mode, or the raw_json policy gate.

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?

Two sentences, front-loaded with the action and resource; no filler or repetition of the tool name. The second sentence is glossary-style context rather than invocation guidance, which is mildly off-purpose for a 15-parameter tool, but it is short and does aid interpretation of results.

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?

For a 15-parameter read tool with no output schema, the description should at least sketch the shape of the returned maintenance objects or the default field set. The schema carries the parameter burden well, but the return-value side is left entirely implicit despite there being no output schema.

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 schema already documents all 15 parameters in detail, including filter vs. search, output modes, and the raw_json policy caveat. The description adds no parameter-level meaning beyond that, 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?

The description uses a specific verb and resource ('Retrieve maintenance periods') and immediately clarifies the domain object it returns, so an agent knows exactly what comes back. It does not name any sibling tool or explain how it differs from e.g. problem_get or host_get, but the resource is distinctive enough that confusion is unlikely.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternatives are named. The patching-window example explains what maintenance windows are rather than when an agent should call this tool instead of, say, problem_get or host_get.

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