Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

problem_get

Read-only

Retrieve unresolved Zabbix problems as raw rows with numeric severities and Unix timestamps for scripts, bulk audits, or advanced filters not exposed by the operator-facing active problems view.

Instructions

Low-level audit retrieval of unresolved Zabbix problems. Returns raw rows with numeric severities and Unix timestamps, no host name, no severity label. For an operator chat question ('what is wrong right now', 'active problems', 'current alerts', 'real problems') call problem_active_get instead -- it returns the same problems but with disabled-trigger/host noise dropped, host names attached, and human-readable time/severity, so the LLM does not have to post-process or chain three tools. Reach for problem_get only when you specifically need raw rows for a script, a bulk audit of every problem (including stale ones), or filters problem_active_get does not expose ('acknowledged', 'suppressed', 'recent', 'time_from', 'time_till'). For historical events (including resolved), use event.get instead. The newest problems come first unless a sort is given.

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: acknowledged, cause_eventid (6.4+), cep_ruleid (8.0+), clock, correlationid, eventid, flags (8.0+), name, ns, object, objectid, r_clock, r_eventid, r_ns, severity, source, userid. Text properties cannot be filtered; use 'search' for them.
objectNoProblem object type: 0=trigger, 1=discovered host, 2=discovered service, 3=autoregistration, 4=item, 5=LLD rule.
outputNoProperties of the problem object to return. Pass 'extend' for all, 'count' for the number of matches only, or a list of property names. Default when omitted: eventid, name, severity, clock, r_clock, objectid. Properties: acknowledged, cause_eventid (6.4+), cep_ruleid (8.0+), clock, correlationid, eventid, flags (8.0+), name, ns, object, objectid, opdata, r_clock, r_eventid, r_ns, severity, source, suppressed, urls, userid.
recentNotrue = also return problems that were resolved a moment ago (for as long as 'Display OK triggers for' in the Zabbix settings says); false or omitted = unresolved problems only. It is not a filter for new problems: use time_from for that.
searchNoReturn results whose string properties contain the given pattern (case-insensitive; '*' is a wildcard when searchWildcardsEnabled is true). Example: {"name": "web"}. Keys: name.
serverNoTarget Zabbix server. Available: default. Defaults to 'default' if omitted.
sourceNoProblem source: 0=trigger (default), 1=discovery, 2=autoregistration, 3=internal.
hostidsNoReturn only problems for the given hosts.
evaltypeNoTag filter evaluation mode: 0=AND/OR (default, all tag conditions must match), 2=OR (any tag condition may match).
eventidsNoReturn only problems with the given event IDs.
groupidsNoReturn only problems for hosts in 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.
monitoredNo[MCP-side filter, applied after the Zabbix call; not a problem.get parameter] If true, drop problems whose trigger is disabled (status != 0) or whose host is disabled (status != 0). Same semantic as host_get's 'monitored' / item_get's 'monitored'. Useful to skip stale problems lingering on de-monitored objects. Default: false (returns every problem Zabbix has on file).
objectidsNoReturn only problems for the given trigger/item/LLD rule IDs.
sortfieldNoSort by one or more of: eventid (a list for several; pair with 'sortorder'). No other property is sortable. When omitted, the result is sorted by eventid with the newest first.
sortorderNoSort order: 'ASC' (ascending) or 'DESC' (descending). 'DESC' while 'sortfield' is omitted (newest first); 'ASC' alone returns the oldest first.
time_fromNoReturn only problems created after this time (Unix timestamp, ISO 8601 date-time such as 2026-04-01T08:00:00Z, or a relative time such as now-1h, now/d or now-7d/d; a value without a zone is read in the zone resolved for the call).
time_tillNoReturn only problems created before this time (Unix timestamp, ISO 8601 date-time such as 2026-04-01T08:00:00Z, or a relative time such as now-1h, now/d or now-7d/d; a value without a zone is read in the zone resolved for the call).
suppressedNoFilter by suppression state: true = only suppressed problems (silenced by a maintenance window or by hand), false = only problems that are not suppressed. Omit it for both.
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).
acknowledgedNoFilter by acknowledgement state: true=acknowledged only, false=unacknowledged only.
extra_paramsNoOther native problem.get parameters, merged into the request as-is. Parameters: action (7.0+), action_userids (7.0+), eventid_from, eventid_till, severities, symptom (6.4+), tags. Sub-object selects (value 'extend', 'count' or a list of property names): selectAcknowledges, selectSuppressionData, selectTags. 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.
severity_minNoMinimum severity to return: 0=not classified, 1=information, 2=warning, 3=average, 4=high, 5=disaster.
searchWildcardsEnabledNoIf true, enable * and ? wildcards in search patterns.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changedv1.42.2
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / evaltype / anyOf
      Previous value: -[
      -  {
      -    "type": "integer"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      0,
      +      2
      +    ],
      +    "type": "integer"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / extra_params / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "propertyNames": {
      +      "enum": [
      +        "editable",
      +        "excludeSearch",
      +        "preservekeys",
      +        "startSearch",
      +        "action",
      +        "action_userids",
      +        "eventid_from",
      +        "eventid_till",
      +        "severities",
      +        "symptom",
      +        "tags",
      +        "applicationids",
      +        "selectAcknowledges",
      +        "selectSuppressionData",
      +        "selectTags"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / filter / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "propertyNames": {
      +      "enum": [
      +        "acknowledged",
      +        "cause_eventid",
      +        "cep_ruleid",
      +        "clock",
      +        "correlationid",
      +        "eventid",
      +        "flags",
      +        "name",
      +        "ns",
      +        "object",
      +        "objectid",
      +        "r_clock",
      +        "r_eventid",
      +        "r_ns",
      +        "severity",
      +        "source",
      +        "userid"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / output / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "extend",
      +      "count"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "acknowledged",
      +        "cause_eventid",
      +        "cep_ruleid",
      +        "clock",
      +        "correlationid",
      +        "eventid",
      +        "flags",
      +        "name",
      +        "ns",
      +        "object",
      +        "objectid",
      +        "opdata",
      +        "r_clock",
      +        "r_eventid",
      +        "r_ns",
      +        "severity",
      +        "source",
      +        "suppressed",
      +        "urls",
      +        "userid"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / output / description
      Previous value: -"Properties of the problem 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: eventid, name, severity, clock, r_clock, objectid. Properties: acknowledged, cause_eventid (6.4+), cep_ruleid (8.0+), clock, correlationid, eventid, flags (8.0+), name, ns, object, objectid, opdata, r_clock, r_eventid, r_ns, severity, source, suppressed, urls, userid."New value: +"Properties of the problem object to return. Pass 'extend' for all, 'count' for the number of matches only, or a list of property names. Default when omitted: eventid, name, severity, clock, r_clock, objectid. Properties: acknowledged, cause_eventid (6.4+), cep_ruleid (8.0+), clock, correlationid, eventid, flags (8.0+), name, ns, object, objectid, opdata, r_clock, r_eventid, r_ns, severity, source, suppressed, urls, userid."
    • changedInput schema / properties / recent / description
      Previous value: -"Return only recently created problems (within the last 30 minutes). Useful for detecting new issues quickly."New value: +"true = also return problems that were resolved a moment ago (for as long as 'Display OK triggers for' in the Zabbix settings says); false or omitted = unresolved problems only. It is not a filter for new problems: use time_from for that."
    • changedInput schema / properties / search / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "propertyNames": {
      +      "enum": [
      +        "name"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / sortfield / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "eventid"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "eventid"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / sortfield / description
      Previous value: -"Sort by one or more of: eventid (comma-separated for several; pair with 'sortorder'). No other property is sortable."New value: +"Sort by one or more of: eventid (a list for several; pair with 'sortorder'). No other property is sortable. When omitted, the result is sorted by eventid with the newest first."
    • 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"
      +  }
      +]
    • changedInput schema / properties / sortorder / description
      Previous value: -"Sort order: 'ASC' (ascending) or 'DESC' (descending)."New value: +"Sort order: 'ASC' (ascending) or 'DESC' (descending). 'DESC' while 'sortfield' is omitted (newest first); 'ASC' alone returns the oldest first."
    • changedInput schema / properties / suppressed / description
      Previous value: -"Filter by suppression state. Suppressed problems are silenced during maintenance windows or by manual suppression."New value: +"Filter by suppression state: true = only suppressed problems (silenced by a maintenance window or by hand), false = only problems that are not suppressed. Omit it for both."
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "result": {
      -      "title": "Result",
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "result"
      -  ],
      -  "title": "problem_getOutput",
      -  "type": "object"
      -}New value: +null
  2. First observedv1.41.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description's job is to add context, and it does: raw unenriched rows, missing host names and severity labels, and default newest-first ordering. It does not mention that responses are wrapped in a prompt-injection preamble unless raw_json is set, but the schema documents that under raw_json, so the gap is minor.

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?

Front-loaded with the core distinction and warning about raw output before the routing guidance. It is dense but almost every clause carries information; the bolded parentheticals are slightly repetitive but not wasteful enough to be a distraction.

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 26-parameter, no-output-schema read tool, the description covers the critical decision (this vs. problem_active_get vs. event.get) and the output's limitations. The return shape is selectable via the schema's output parameter, so omitting field-level detail is acceptable; only the security-preamble behavior is left unmentioned in the prose.

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 all 26 parameters are already documented in the schema, which sets the baseline at 3. The description adds a little value by flagging the filter parameters and the default sort behavior ('newest problems come first unless a sort is given'), but it does not explain semantics of parameters beyond what the schema supplies.

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 ('low-level audit retrieval of unresolved Zabbix problems') and immediately distinguishes the output shape ('raw rows with numeric severities and Unix timestamps, no host name, no severity label'). It also names the sibling that does the opposite, so an agent can pick correctly without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use routing: operator chat questions go to problem_active_get, scripted/bulk audits stay here, historical/resolved goes to event.get. It even enumerates the filters only this tool exposes ('acknowledged', 'suppressed', 'recent', 'time_from', 'time_till'), leaving nothing to inference.

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