Zabbix MCP Server

Overview Schema Source Related Servers Discussions Admin

discoveryruleprototype_get

Read-only

Retrieve LLD rule prototypes from Zabbix 7.4+ to inspect nested discovery rules and filter, search, sort, or count matching results.

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

Name	Required	Description
`limit`	No	Maximum number of results to return.
`filter`	No	Return 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, request_method, retrieve_mode, snmp_oid, ssl_cert_file, ssl_key_file, ssl_key_password, status, status_codes, 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.
`output`	No	Properties of the discoveryruleprototype object to return. Pass 'extend' for all, 'count' for the number of matches only, or a 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, templateid, time_shift (8.0+), timeout, trapper_hosts, trends, type, units, url, username, uuid, value_type, valuemapid, verify_host, verify_peer.
`search`	No	Return 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.
`server`	No	Target Zabbix server. Available: default. Defaults to 'default' if omitted.
`hostids`	No	Return only LLD rule prototypes that belong to the given hosts.
`raw_json`	No	Strips 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.
`sortfield`	No	Sort by one or more of: itemid, name, key_, delay, type, status, discover (a list for several; pair with 'sortorder'). No other property is sortable.
`sortorder`	No	Sort order: 'ASC' (ascending) or 'DESC' (descending).
`countOutput`	No	Return the count of matching results instead of the actual data.
`searchByAny`	No	If true, return results matching ANY search field (OR). Default is ALL fields (AND).
`discoveryids`	No	Return only LLD rule prototypes with the given IDs.
`extra_params`	No	Other native discoveryruleprototype.get parameters, merged into the request as-is. Parameters: groupCount, groupids, inherited, interfaceids, itemids, limitSelects, monitored, templated, templateids. Switches (true turns one on, false is the same as leaving it out): groupCount. groupCount goes with output='count': the count is then split by the ID filters the method groups by (hostids, groupids ...), one row per ID with 'rowscount'; a single row without such a filter. Sub-object selects (value 'extend', 'count' or a list of property names): selectDiscoveryData, 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.
`searchWildcardsEnabled`	No	If true, enable * and ? wildcards in search patterns.

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedv1.42.2Nov 7, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / properties / extra_params / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "propertyNames": {
+      "enum": [
+        "editable",
+        "excludeSearch",
+        "preservekeys",
+        "startSearch",
+        "groupCount",
+        "groupids",
+        "inherited",
+        "interfaceids",
+        "itemids",
+        "limitSelects",
+        "monitored",
+        "templated",
+        "templateids",
+        "selectDiscoveryData",
+        "selectDiscoveryRule",
+        "selectDiscoveryRulePrototype",
+        "selectDiscoveryRulePrototypes",
+        "selectFilter",
+        "selectGraphs",
+        "selectHostPrototypes",
+        "selectHosts",
+        "selectItems",
+        "selectLLDMacroPaths",
+        "selectOverrides",
+        "selectPreprocessing",
+        "selectTriggers"
+      ]
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / extra_params / description

Previous value: -"Other 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."New value: +"Other native discoveryruleprototype.get parameters, merged into the request as-is. Parameters: groupCount, groupids, inherited, interfaceids, itemids, limitSelects, monitored, templated, templateids. Switches (true turns one on, false is the same as leaving it out): groupCount. groupCount goes with output='count': the count is then split by the ID filters the method groups by (hostids, groupids ...), one row per ID with 'rowscount'; a single row without such a filter. Sub-object selects (value 'extend', 'count' or a list of property names): selectDiscoveryData, 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."

changedInput schema / properties / filter / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "propertyNames": {
+      "enum": [
+        "allow_traps",
+        "authtype",
+        "delay",
+        "discover",
+        "enabled_lifetime",
+        "enabled_lifetime_type",
+        "flags",
+        "follow_redirects",
+        "granularity",
+        "history",
+        "hostid",
+        "http_proxy",
+        "interfaceid",
+        "inventory_link",
+        "ipmi_sensor",
+        "itemid",
+        "jmx_endpoint",
+        "key_",
+        "lifetime",
+        "lifetime_type",
+        "logtimefmt",
+        "lookback_limit",
+        "master_itemid",
+        "name",
+        "output_format",
+        "password",
+        "post_type",
+        "privatekey",
+        "publickey",
+        "request_method",
+        "retrieve_mode",
+        "snmp_oid",
+        "ssl_cert_file",
+        "ssl_key_file",
+        "ssl_key_password",
+        "status",
+        "status_codes",
+        "templateid",
+        "time_shift",
+        "timeout",
+        "trapper_hosts",
+        "trends",
+        "type",
+        "units",
+        "url",
+        "username",
+        "uuid",
+        "value_type",
+        "valuemapid",
+        "verify_host",
+        "verify_peer"
+      ]
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / filter / description

Previous value: -"Return 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."New value: +"Return 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, request_method, retrieve_mode, snmp_oid, ssl_cert_file, ssl_key_file, ssl_key_password, status, status_codes, 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."

changedInput schema / properties / output / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "extend",
+      "count"
+    ],
+    "type": "string"
+  },
+  {
+    "items": {
+      "enum": [
+        "allow_traps",
+        "authtype",
+        "delay",
+        "description",
+        "discover",
+        "enabled_lifetime",
+        "enabled_lifetime_type",
+        "error",
+        "flags",
+        "follow_redirects",
+        "granularity",
+        "headers",
+        "history",
+        "hostid",
+        "http_proxy",
+        "interfaceid",
+        "inventory_link",
+        "ipmi_sensor",
+        "itemid",
+        "jmx_endpoint",
+        "key_",
+        "lifetime",
+        "lifetime_type",
+        "logtimefmt",
+        "lookback_limit",
+        "master_itemid",
+        "name",
+        "output_format",
+        "parameters",
+        "params",
+        "password",
+        "post_type",
+        "posts",
+        "privatekey",
+        "publickey",
+        "query",
+        "query_fields",
+        "request_method",
+        "retrieve_mode",
+        "ruleid",
+        "snmp_oid",
+        "ssl_cert_file",
+        "ssl_key_file",
+        "ssl_key_password",
+        "state",
+        "status",
+        "status_codes",
+        "templateid",
+        "time_shift",
+        "timeout",
+        "trapper_hosts",
+        "trends",
+        "type",
+        "units",
+        "url",
+        "username",
+        "uuid",
+        "value_type",
+        "valuemapid",
+        "verify_host",
+        "verify_peer"
+      ],
+      "type": "string"
+    },
+    "minItems": 1,
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / output / description

Previous value: -"Properties 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."New value: +"Properties of the discoveryruleprototype object to return. Pass 'extend' for all, 'count' for the number of matches only, or a 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, templateid, time_shift (8.0+), timeout, trapper_hosts, trends, type, units, url, username, uuid, value_type, valuemapid, verify_host, verify_peer."

changedInput schema / properties / search / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "propertyNames": {
+      "enum": [
+        "delay",
+        "description",
+        "enabled_lifetime",
+        "granularity",
+        "history",
+        "http_proxy",
+        "ipmi_sensor",
+        "jmx_endpoint",
+        "key_",
+        "lifetime",
+        "logtimefmt",
+        "lookback_limit",
+        "name",
+        "params",
+        "password",
+        "posts",
+        "privatekey",
+        "publickey",
+        "snmp_oid",
+        "ssl_cert_file",
+        "ssl_key_file",
+        "ssl_key_password",
+        "status_codes",
+        "time_shift",
+        "timeout",
+        "trapper_hosts",
+        "trends",
+        "units",
+        "url",
+        "username",
+        "uuid"
+      ]
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / sortfield / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "itemid",
+      "name",
+      "key_",
+      "delay",
+      "type",
+      "status",
+      "discover"
+    ],
+    "type": "string"
+  },
+  {
+    "items": {
+      "enum": [
+        "itemid",
+        "name",
+        "key_",
+        "delay",
+        "type",
+        "status",
+        "discover"
+      ],
+      "type": "string"
+    },
+    "minItems": 1,
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / sortfield / description

Previous value: -"Sort by one or more of: itemid, name, key_, delay, type, status (comma-separated for several; pair with 'sortorder'). No other property is sortable."New value: +"Sort by one or more of: itemid, name, key_, delay, type, status, discover (a list for several; pair with 'sortorder'). No other property is sortable."

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"
+  }
+]

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "discoveryruleprototype_getOutput",
-  "type": "object"
-}New value: +null

First observedv1.41.0Oct 20, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the version constraint and conceptual context for nested discovery, but does not disclose result format, pagination, permissions, or filtering behavior beyond what the annotations provide.

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

Conciseness5/5

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

The description is two sentences, front-loaded with the core action and resource, and the second sentence supplies useful conceptual context without waste.

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?

The description identifies the tool and explains the LLD prototype concept, while the schema fully documents parameters and annotations cover read-only safety. However, for a 14-parameter retrieval tool, it omits usage context relative to sibling tools and does not describe the default output behavior in the description.

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 input schema already documents all 14 parameters thoroughly. The description adds no parameter-specific meaning, so the baseline of 3 is appropriate.

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?

The description states a specific verb and resource: 'Retrieve LLD rule prototypes.' It also explains what LLD rule prototypes are and notes the Zabbix 7.4+ version. It does not explicitly differentiate this tool from the sibling discoveryrule_get, so it falls 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 Guidelines2/5

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

The description provides no explicit guidance on when to use this tool versus alternatives such as discoveryrule_get or other prototype retrieval tools. It describes the resource but not selection conditions, exclusions, or prerequisites.

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

Deploy Server

discoveryruleprototype_get

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools