Skip to main content
Glama
initMAX

Zabbix MCP Server

discoveryrule_get

Read-only

Retrieve Low-Level Discovery (LLD) rules to discover host entities such as filesystems, network interfaces, and SNMP OIDs, and generate items, triggers, and graphs from prototypes.

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

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 (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.
outputNoProperties 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.
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 (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).
templateidsNoReturn only LLD rules that belong to the given templates.
extra_paramsNoOther 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.
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.2/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 genuine domain semantics (LLD rules discover entities and generate items, triggers, and graphs from prototypes, and return JSON), but it says nothing about permissions, result volume, or the prompt-injection-wrapping/raw_json behavior that the schema documents. Useful context, but not behavioral disclosure beyond annotations.

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 compact sentences, front-loaded with the action and resource, then two sentences of focused background. Every sentence carries information, though the two explanatory sentences are tutorial material that could be trimmed for an agent that already knows Zabbix LLD.

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 and the rich property list need not be re-explained, and the schema fully covers parameters. What is missing is invocation context: which of the 15 filters to reach for, how this tool relates to its many sibling *_get tools, and any prerequisite/authentication notes. Adequate but with clear gaps for a 15-parameter read tool.

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 15 parameters, so the schema already documents limit, filter, output, search, raw_json, extra_params and the rest in detail. The description contributes no parameter-level meaning at all, making the baseline 3 the correct score.

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 opens with a concrete verb and resource ('Retrieve Low-Level Discovery (LLD) rules') and goes on to explain what an LLD rule fundamentally is (a special item returning JSON about discovered entities). This clearly separates it from generic item_get-style tools, though it never names a sibling such as discoveryruleprototype_get or item_get to sharpen the distinction.

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 when-to-use or when-not-to-use guidance anywhere in the description. It never states when an agent should call discoveryrule_get rather than item_get, discoveryruleprototype_get, or the raw-call escape hatch mentioned only in the schema's extra_params field. Usage is left entirely to inference from the resource name.

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