Skip to main content
Glama
initMAX

Zabbix MCP Server

discoveryruleprototype_get

Read-only

Fetch LLD rule prototypes to create multi-level discovery in Zabbix, enabling discovery rules on hosts discovered by parent rules.

Instructions

Retrieve LLD rule prototypes (Zabbix 7.4+). LLD rule prototypes allow discovery rules to be created on hosts that are themselves discovered by a parent LLD rule, enabling multi-level (nested) discovery.

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: allow_traps, authtype, delay, discover, enabled_lifetime, enabled_lifetime_type, flags, follow_redirects, granularity (8.0+), history, hostid, http_proxy, interfaceid, inventory_link, ipmi_sensor, itemid, jmx_endpoint, key_, lifetime, lifetime_type, logtimefmt, lookback_limit (8.0+), master_itemid, name, output_format, password, post_type, privatekey, publickey, query (8.0+), request_method, retrieve_mode, snmp_oid, ssl_cert_file, ssl_key_file, ssl_key_password, status, status_codes, storage_mode (8.0+), templateid, time_shift (8.0+), timeout, trapper_hosts, trends, type, units, url, username, uuid, value_type, valuemapid, verify_host, verify_peer. Text properties cannot be filtered; use 'search' for them.
outputNoProperties of the discoveryruleprototype 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: itemid, hostid, name, key_, status. Properties: allow_traps, authtype, delay, description, discover, enabled_lifetime, enabled_lifetime_type, error, flags, follow_redirects, granularity (8.0+), headers, history, hostid, http_proxy, interfaceid, inventory_link, ipmi_sensor, itemid, jmx_endpoint, key_, lifetime, lifetime_type, logtimefmt, lookback_limit (8.0+), master_itemid, name, output_format, parameters, params, password, post_type, posts, privatekey, publickey, query (8.0+), query_fields, request_method, retrieve_mode, ruleid, snmp_oid, ssl_cert_file, ssl_key_file, ssl_key_password, state, status, status_codes, storage_mode (8.0+), templateid, time_shift (8.0+), timeout, trapper_hosts, trends, type, units, url, username, uuid, value_type, valuemapid, verify_host, verify_peer.
searchNoReturn results whose string properties contain the given pattern (case-insensitive; '*' is a wildcard when searchWildcardsEnabled is true). Example: {"name": "web"}. Keys: delay, description, enabled_lifetime, granularity (8.0+), history, http_proxy, ipmi_sensor, jmx_endpoint, key_, lifetime, logtimefmt, lookback_limit (8.0+), name, params, password, posts, privatekey, publickey, snmp_oid, ssl_cert_file, ssl_key_file, ssl_key_password, status_codes, time_shift (8.0+), timeout, trapper_hosts, trends, units, url, username, uuid.
serverNoTarget Zabbix server. Available: default. Defaults to 'default' if omitted.
hostidsNoReturn only LLD rule 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: itemid, name, key_, delay, type, status (comma-separated 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).
discoveryidsNoReturn only LLD rule prototypes with the given IDs.
extra_paramsNoOther native discoveryruleprototype.get parameters, merged into the request as-is. Parameters: groupids, inherited, interfaceids, itemids, limitSelects, monitored, templated, templateids. Sub-object selects (value 'extend', 'count' or a list of property names): selectDiscoveryRule, selectDiscoveryRulePrototype, selectDiscoveryRulePrototypes, selectFilter, selectGraphs, selectHostPrototypes, selectHosts, selectItems, selectLLDMacroPaths, selectOverrides, selectPreprocessing, selectTriggers. 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

A3.5/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 by structured data. The description adds useful conceptual context (nested discovery, version requirement) but says nothing about response size, rate limits, or permission needs beyond what annotations and the limit/pagination params already convey.

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 verb and resource, followed by a compact conceptual note. Nothing is redundant or padding, though the second sentence is explanatory rather than operational.

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 an output schema present and fully-described parameters, the description only needs to establish purpose and the version prerequisite, which it does. The main remaining gap is not pointing to the sibling tools that handle non-nested rules or lower Zabbix versions.

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% and every parameter (filter, output, search, raw_json, extra_params, etc.) is documented in the schema itself. The description contributes no additional parameter meaning, 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?

Clear verb ('Retrieve') plus a specific resource ('LLD rule prototypes'), and the second sentence explains what a prototype is in the multi-level discovery model. It does not explicitly distinguish itself from the neighboring discoveryrule_get (actual rules) or itemprototype_get, so it stops short of a 5.

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

Usage Guidelines3/5

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

The version gate 'Zabbix 7.4+' is a real usage constraint that a caller must respect. However, there is no when-to-use/when-not guidance and no routing to alternatives such as discoveryrule_get for regular (non-nested) LLD rules, leaving selection to inference.

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