Skip to main content
Glama
initMAX

Zabbix MCP Server

trigger_get

Read-only

Retrieve Zabbix triggers to inspect expressions, severity, and problem state, enabling detection of active issues and host health monitoring.

Instructions

Retrieve triggers. Triggers define conditions (expressions) that evaluate item values and determine when a problem exists. Each trigger references one or more items via an expression like 'last(/host/key) > 90'. Triggers have severity levels (0-5) and generate events when their state changes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return.
activeNoOnly return enabled triggers that belong to enabled hosts.
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: correlation_mode, correlation_tag, description, error, event_name (6.0+), expression, flags, lastchange, manual_close, opdata, priority, recovery_expression, recovery_mode, state, status, templateid, triggerid, type, url, url_name (6.4+), uuid (6.0+), value. Text properties cannot be filtered; use 'search' for them.
outputNoProperties of the trigger 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: triggerid, description, priority, status, value. Properties: comments, correlation_mode, correlation_tag, description, error, event_name (6.0+), expression, flags, lastchange, manual_close, opdata, priority, recovery_expression, recovery_mode, state, status, templateid, triggerid, type, url, url_name (6.4+), uuid (6.0+), value.
searchNoReturn results whose string properties contain the given pattern (case-insensitive; '*' is a wildcard when searchWildcardsEnabled is true). Example: {"name": "web"}. Keys: comments, correlation_tag, description, error, event_name (6.0+), expression, opdata, recovery_expression, url, url_name (6.4+), uuid (6.0+).
serverNoTarget Zabbix server. Available: default. Defaults to 'default' if omitted.
hostidsNoReturn only triggers that belong to the given hosts.
groupidsNoReturn only triggers that belong to 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.
monitoredNoOnly return enabled triggers that belong to enabled hosts and contain only enabled items.
only_trueNoOnly return triggers that are currently in a problem (PROBLEM) state.
sortfieldNoSort by one or more of: triggerid, description, status, priority, lastchange, hostname (comma-separated for several; pair with 'sortorder'). No other property is sortable.
sortorderNoSort order: 'ASC' (ascending) or 'DESC' (descending).
triggeridsNoReturn only triggers with the given IDs.
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).
templateidsNoReturn only triggers that belong to the given templates.
extra_paramsNoOther native trigger.get parameters, merged into the request as-is. Parameters: dependent, evaltype, expandComment, expandDescription, expandExpression, functions, group, host, inherited, inheritedTags (8.0+), itemids, lastChangeSince, lastChangeTill, limitSelects, maintenance, skipDependent, tags, templated, withAcknowledgedEvents, withLastEventUnacknowledged, withUnacknowledgedEvents. Sub-object selects (value 'extend', 'count' or a list of property names): selectDependencies, selectDiscoveryData (7.4+), selectDiscoveryRule, selectFunctions, selectGroups (removed in 7.2), selectHostGroups (6.2+), selectHosts, selectInheritedTags (8.0+), selectItems, selectLastEvent, selectTags, selectTemplateGroups (6.2+), selectTriggerDiscovery. 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.
min_severityNoMinimum trigger severity to return (0-5: NOT_CLASSIFIED, INFORMATION, WARNING, AVERAGE, HIGH, DISASTER)
searchWildcardsEnabledNoIf true, enable * and ? wildcards in search patterns.
with_unacknowledged_eventsNoOnly return triggers that have unacknowledged problem events.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.41.0

TDQS

B3.1/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 (expressions, severity 0-5, event generation) but no operational behavior such as pagination, default result shape, or the raw_json policy nuance that the schema carries.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with 'Retrieve triggers', but three of the four sentences are background education on what triggers are rather than actionable information for calling the tool. Not bloated, but a large share of the text does not earn its place for invocation.

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?

An output schema exists, so return values need no explanation, and all parameters are documented in the schema. The gap is that a 21-parameter, complex query tool offers no guidance on scope or alternatives, leaving the description merely adequate rather than complete.

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 21 parameters, including detailed filter/search/output keys, so the schema does the heavy lifting. The description adds no parameter meaning beyond what is already structured, making the baseline 3 correct.

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?

Opens with a specific verb+resource ('Retrieve triggers') that an agent can act on, and the following sentences define what a trigger is. However, it never distinguishes this tool from close siblings such as triggerprototype_get or problem_get, so selection still requires inference.

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 is purely definitional about triggers; it gives no when-to-use context, no prerequisites, and no alternatives. With siblings like triggerprototype_get, event_get, and problem_get present, the agent gets no routing help.

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