Skip to main content
Glama
initMAX

Zabbix MCP Server

drule_get

Read-only

Retrieve Zabbix network discovery rules to inspect IP ranges and checks used to automatically find new hosts and services.

Instructions

Retrieve network discovery rules. Network discovery rules define IP ranges and checks (SNMP, agent, ICMP, etc.) used to automatically find new hosts on the network. Discovered hosts and services are stored as dhost/dservice objects.

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: concurrency_max (7.0+), delay, druleid, error (7.0+), iprange, name, nextcheck (removed in 6.4), proxy_hostid (removed in 7.0), proxyid (7.0+), status. Text properties cannot be filtered; use 'search' for them.
outputNoProperties of the drule 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: druleid, name, status. Properties: concurrency_max (7.0+), delay, druleid, error (7.0+), iprange, name, nextcheck (removed in 6.4), proxy_hostid (removed in 7.0), proxyid (7.0+), status.
searchNoReturn results whose string properties contain the given pattern (case-insensitive; '*' is a wildcard when searchWildcardsEnabled is true). Example: {"name": "web"}. Keys: delay, error (7.0+), iprange, name.
serverNoTarget Zabbix server. Available: default. Defaults to 'default' if omitted.
druleidsNoReturn only network discovery rules with the given 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: druleid, name (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).
extra_paramsNoOther native drule.get parameters, merged into the request as-is. Parameters: dhostids, dserviceids, limitSelects. Sub-object selects (value 'extend', 'count' or a list of property names): selectDChecks, selectDHosts. 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.6/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 domain context (rules define IP ranges/checks, results land in dhost/dservice objects) but says nothing about return volume, pagination, or the raw_json/security-preamble behavior that the schema documents.

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?

Two sentences, the core action front-loaded and the domain explanation kept tight. Nothing is padded or repeated.

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 full parameter documentation, the description need not explain return values. It adequately frames what the tool reads and where the resulting data lives; only the absence of routing guidance to sibling tools keeps it from being fully 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 every one of the 13 parameters carries a detailed description, so the schema does the heavy lifting. The description contributes no parameter-level meaning beyond it, making the baseline 3 correct.

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 and resource ('Retrieve network discovery rules') and disambiguates the domain from similar-sounding siblings such as discoveryrule_get (LLD) and dcheck_get by explaining that these rules define IP ranges and checks. It stops short of naming an alternative tool explicitly, so it is clear but not sibling-routing.

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?

Usage is only implied: an agent can infer this is the read entry point for network discovery configuration, but there is no statement of when to use it versus dcheck_get, dhost_get, or discoveryrule_get, and no prerequisites or exclusions.

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