Skip to main content
Glama
initMAX

Zabbix MCP Server

problem_get

Read-only

Retrieves raw unresolved Zabbix problems for scripts, bulk audits, or filters not exposed by active problem tools (acknowledged, suppressed, time ranges).

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.

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: 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 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.
recentNoReturn only recently created problems (within the last 30 minutes). Useful for detecting new issues quickly.
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 (comma-separated for several; pair with 'sortorder'). No other property is sortable.
sortorderNoSort order: 'ASC' (ascending) or 'DESC' (descending).
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. Suppressed problems are silenced during maintenance windows or by manual suppression.
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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.41.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say readOnly=true and openWorld=true; the description goes well beyond by disclosing the degraded output contract (no host name, no severity label, numeric severities, Unix timestamps) and the downstream cost (LLM must post-process or chain three tools). It also warns that everything including stale problems is returned by default. This is exactly the behavior an agent cannot infer from the schema or annotations.

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 purpose and output caveat before the routing advice, and nearly every clause carries decision-relevant information. It is a dense paragraph rather than bulleted, and the parenthetical filter list is somewhat sprawling, but there is little filler to cut.

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

Completeness5/5

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

For a 26-parameter, zero-required, 100%-documented schema with an output schema present, the description supplies the missing decision context (when to choose this over siblings, what the raw output lacks) rather than repeating return values. An agent has everything needed to select and invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 and the schema carries the parameter detail. The description adds genuine routing value by naming the filter keys unique to this tool ('acknowledged', 'suppressed', 'recent', 'time_from', 'time_till'), which tells the agent why it would pick problem_get over problem_active_get. It does not add format/syntax beyond the schema, so it stays below 5.

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+resource ('low-level audit retrieval of unresolved Zabbix problems') and immediately characterizes the output shape ('raw rows with numeric severities and Unix timestamps'). It explicitly distinguishes itself from two named siblings (problem_active_get, event.get) so an agent can route without opening any 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 the operator-chat use case verbatim ('what is wrong right now', 'active problems') and directs it to problem_active_get, then enumerates the three narrow conditions under which problem_get is the right call (scripting, bulk audit including stale rows, filters the alternative lacks). It also routes historical/resolved queries to event.get, so both when-not and alternatives are covered.

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