Skip to main content
Glama
initMAX

Zabbix MCP Server

triggerprototype_get

Read-only

Retrieve trigger prototypes used by LLD rules to create real triggers for discovered entities, filtering by host, template, or discovery rule.

Instructions

Retrieve trigger prototypes. Trigger prototypes are used by LLD rules to create real triggers for each discovered entity. Their expressions reference item prototypes and use LLD macros.

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: correlation_mode, correlation_tag, description, discover, event_name (6.0+), expression, flags (7.4+), manual_close, opdata, priority, recovery_expression, recovery_mode, status, templateid, triggerid, type, url, url_name (6.4+), uuid (6.0+). Text properties cannot be filtered; use 'search' for them.
outputNoProperties of the triggerprototype 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. Properties: comments, correlation_mode, correlation_tag, description, discover, error (removed in 8.0), event_name (6.0+), expression, flags (7.4+), lastchange (removed in 8.0), manual_close, opdata, priority, recovery_expression, recovery_mode, state (removed in 8.0), status, templateid, triggerid, type, url, url_name (6.4+), uuid (6.0+), value (removed in 8.0).
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, 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 trigger prototypes that belong to the given hosts.
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: triggerid, description, status, priority, discover (comma-separated for several; pair with 'sortorder'). No other property is sortable.
sortorderNoSort order: 'ASC' (ascending) or 'DESC' (descending).
triggeridsNoReturn only trigger prototypes 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 trigger prototypes that belong to the given templates.
discoveryidsNoReturn only trigger prototypes belonging to the given LLD rules.
extra_paramsNoOther native triggerprototype.get parameters, merged into the request as-is. Parameters: active, expandExpression, functions, group, groupids, host, inherited, limitSelects, maintenance, min_severity, monitored, templated. Sub-object selects (value 'extend', 'count' or a list of property names): selectDependencies, selectDiscoveryData (7.4+), selectDiscoveryRule, selectDiscoveryRulePrototype (7.4+), selectFunctions, selectGroups (removed in 7.2), selectHostGroups (6.2+), selectHosts, selectInheritedTags (8.0+), selectItems, selectTags, selectTemplateGroups (6.2+). 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.
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.1/5.0
Behavior2/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 vocabulary (LLD macros, expression/item-prototype relationships) but no operational behavior—nothing about pagination, default limits, permissions, or scope of returned data.

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 tightly written sentences, front-loaded with the action and resource. The second sentence is explanatory rather than wasteful, though it stops short of routing the agent toward correct usage.

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?

With a rich 16-parameter schema, full description coverage, an output schema, and safety annotations in place, the description only needs to establish what the resource is—which it does. Nothing critical for correct invocation is missing, though alternatives routing would help.

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 fully documents all 16 parameters and the baseline is 3. The description contributes no parameter-level detail beyond what the schema already provides.

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 ('Retrieve') and resource ('trigger prototypes') and adds domain context via the definitional second sentence about LLD rules and item prototypes. It separates itself conceptually from trigger_get and itemprototype_get, though it never names or contrasts those siblings explicitly.

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 statement of when to use this tool versus alternatives such as trigger_get or the other *_prototype_get siblings, and no prerequisites or exclusions. Usage is only implied by the definitional context.

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