Skip to main content
Glama
Sign In
Zabbix MCP Server

Zabbix MCP Server

by initMAX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

discoveryrule_get

Read-only

Retrieve Low-Level Discovery (LLD) rules from Zabbix to inspect automatic discovery configurations for hosts and templates, with filtering and sorting options.

Instructions

Retrieve Low-Level Discovery (LLD) rules. LLD rules automatically discover entities on a host (filesystems, network interfaces, SNMP OIDs, etc.) and create items, triggers, and graphs from prototypes for each discovered entity. LLD rules are special items that return JSON describing the discovered entities.

Input 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 (7.0+), enabled_lifetime_type (7.0+), flags (7.4+), follow_redirects, granularity (8.0+), history, hostid, http_proxy, interfaceid, inventory_link, ipmi_sensor, itemid, jmx_endpoint, key_, lifetime, lifetime_type (7.0+), 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, state, status, status_codes, templateid, time_shift (8.0+), timeout, trapper_hosts, trends, type, units, url, username, uuid (6.0+), value_type, valuemapid, verify_host, verify_peer. Text properties cannot be filtered; use 'search' for them.
outputNoProperties of the discoveryrule 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 (7.0+), enabled_lifetime_type (7.0+), error, flags (7.4+), follow_redirects, granularity (8.0+), headers, history, hostid, http_proxy, interfaceid, inventory_link, ipmi_sensor, itemid, jmx_endpoint, key_, lifetime, lifetime_type (7.0+), logtimefmt, lookback_limit (8.0+), master_itemid, name, output_format, parameters (6.0+), params, password, post_type, posts, privatekey, publickey, query (8.0+), query_fields, request_method, retrieve_mode, 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 (6.0+), 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 (7.0+), error, 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, units, url, username, uuid (6.0+).
serverNoTarget Zabbix server. Available: default. Defaults to 'default' if omitted.
hostidsNoReturn only LLD rules that belong to the given hosts.
itemidsNoReturn only LLD rules with the given IDs (LLD rules use item IDs).
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 (a list 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).
templateidsNoReturn only LLD rules that belong to the given templates.
extra_paramsNoOther native discoveryrule.get parameters, merged into the request as-is. Parameters: groupCount, groupids, inherited, interfaceids, limitSelects, monitored, templated. 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 (7.4+), selectDiscoveryRule (7.4+), selectDiscoveryRulePrototypes (7.4+), 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv1.42.2
    • 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",
+        "limitSelects",
+        "monitored",
+        "templated",
+        "selectDiscoveryData",
+        "selectDiscoveryRule",
+        "selectDiscoveryRulePrototypes",
+        "selectFilter",
+        "selectGraphs",
+        "selectHostPrototypes",
+        "selectHosts",
+        "selectItems",
+        "selectLLDMacroPaths",
+        "selectOverrides",
+        "selectPreprocessing",
+        "selectTriggers",
+        "selectApplicationPrototypes"
+      ]
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / extra_params / description
      Previous value: -"Other native discoveryrule.get parameters, merged into the request as-is. Parameters: groupids, inherited, interfaceids, limitSelects, monitored, templated. Sub-object selects (value 'extend', 'count' or a list of property names): selectDiscoveryData (7.4+), selectDiscoveryRulePrototypes (7.4+), 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 discoveryrule.get parameters, merged into the request as-is. Parameters: groupCount, groupids, inherited, interfaceids, limitSelects, monitored, templated. 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 (7.4+), selectDiscoveryRule (7.4+), selectDiscoveryRulePrototypes (7.4+), 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",
+        "state",
+        "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 (7.0+), enabled_lifetime_type (7.0+), flags (7.4+), follow_redirects, granularity (8.0+), history, hostid, http_proxy, interfaceid, inventory_link, ipmi_sensor, itemid, jmx_endpoint, key_, lifetime, lifetime_type (7.0+), 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, state, status, status_codes, storage_mode (8.0+), templateid, time_shift (8.0+), timeout, trapper_hosts, trends, type, units, url, username, uuid (6.0+), 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 (7.0+), enabled_lifetime_type (7.0+), flags (7.4+), follow_redirects, granularity (8.0+), history, hostid, http_proxy, interfaceid, inventory_link, ipmi_sensor, itemid, jmx_endpoint, key_, lifetime, lifetime_type (7.0+), 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, state, status, status_codes, templateid, time_shift (8.0+), timeout, trapper_hosts, trends, type, units, url, username, uuid (6.0+), 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",
+        "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 discoveryrule 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 (7.0+), enabled_lifetime_type (7.0+), error, flags (7.4+), follow_redirects, granularity (8.0+), headers, history, hostid, http_proxy, interfaceid, inventory_link, ipmi_sensor, itemid, jmx_endpoint, key_, lifetime, lifetime_type (7.0+), logtimefmt, lookback_limit (8.0+), master_itemid, name, output_format, parameters (6.0+), params, password, post_type, posts, privatekey, publickey, query (8.0+), query_fields, request_method, retrieve_mode, 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 (6.0+), value_type, valuemapid, verify_host, verify_peer."New value: +"Properties of the discoveryrule 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 (7.0+), enabled_lifetime_type (7.0+), error, flags (7.4+), follow_redirects, granularity (8.0+), headers, history, hostid, http_proxy, interfaceid, inventory_link, ipmi_sensor, itemid, jmx_endpoint, key_, lifetime, lifetime_type (7.0+), logtimefmt, lookback_limit (8.0+), master_itemid, name, output_format, parameters (6.0+), params, password, post_type, posts, privatekey, publickey, query (8.0+), query_fields, request_method, retrieve_mode, 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 (6.0+), 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",
+        "error",
+        "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",
+        "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"
+    ],
+    "type": "string"
+  },
+  {
+    "items": {
+      "enum": [
+        "itemid",
+        "name",
+        "key_",
+        "delay",
+        "type",
+        "status"
+      ],
+      "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 (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": "discoveryrule_getOutput",
-  "type": "object"
-}New value: +null
  2. First observedv1.41.0

TDQS

B3.4/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 and the description only adds conceptual domain context about what LLD rules do. It says nothing operational beyond that — no pagination/limit behavior, no note that the tool defaults to a trimmed field set, and no mention of the security-wrapped response or the multi-server 'server' parameter.

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?

Three sentences, front-loaded with the action, and each adds something: what it returns, what it produces downstream, and that LLD rules are a special item type emitting JSON. No filler, though the middle explanation of items/triggers/graphs is slightly more background than an agent strictly needs to call the tool.

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?

For a 15-parameter read tool with no output schema, the definition covers the purpose and object model but omits operational context an agent would benefit from: the default returned field subset when 'output' is omitted, the countOutput/count equivalence, and the multi-server scoping via 'server'. It is adequate, not 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% and the schema itself is unusually rich (filter/search key enums, output=extend/count, the raw_json policy warning, and the extra_params escape hatch with a pointer to zabbix_raw_api_call). The description adds no parameter-level meaning beyond that, so the baseline of 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?

Opens with a specific verb+resource ("Retrieve Low-Level Discovery (LLD) rules") and then defines the domain object, so an agent that doesn't know Zabbix LLD still understands what is being fetched. It does not explicitly distinguish itself from close siblings such as discoveryruleprototype_get or drule_get, which is the only thing separating it from 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 description implies usage (fetch LLD rules when you need their configuration/discovery data) and clarifies that LLD rules are items that emit JSON, which helps indirectly. But there is no explicit when-to-use/when-not guidance and no named alternative — an agent must infer from sibling names whether to use item_get, discoveryruleprototype_get, or drule_get instead.

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

Deploy Server

Other Tools