Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

Drule Get

drule_get
Read-onlyIdempotent

Retrieve Zabbix network discovery rules to review scanning configurations for hosts and services, with filtering and paging to inspect specific rules or counts.

Instructions

Get network discovery rules from Zabbix.

Network discovery (drule) rules perform network scanning to discover hosts and services. They can scan for active devices, open ports, and available services in CIDR ranges.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "drule_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return. Default is 100.
offsetNoNumber of matching records to skip. Use with 'limit' to page through results; check 'has_more' and 'total' in the response.
outputNoextend
searchNoDictionary with search criteria like {'name': 'LAN'}.
druleidsNoList of network discovery rule IDs to get. Omit to return all rules; an empty list matches none.
sortfieldNoField to sort by. A deterministic sort is required for paging to be consistent.druleid
sortorderNoSort direction - 'ASC' or 'DESC'.ASC
count_outputNoIf true, returns only the count of matched objects as an integer.
filter_paramsNoAdditional filter parameters for advanced filtering.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.7.1
    • changedInput schema / properties / druleids / description
      Previous value: -"List of network discovery rule IDs to get. If empty, returns all rules."New value: +"List of network discovery rule IDs to get. Omit to return all rules; an empty list matches none."
  2. Changed5 schema fields changedv0.6.0
    • changedInput schema / properties / offset / description
      Previous value: -"Number of results to skip (for pagination). Requires sortfield to be set."New value: +"Number of matching records to skip. Use with 'limit' to page through results; check 'has_more' and 'total' in the response."
    • removedInput schema / properties / sortfield / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • changedInput schema / properties / sortfield / default
      Previous value: -nullNew value: +"druleid"
    • changedInput schema / properties / sortfield / description
      Previous value: -"Field to sort by."New value: +"Field to sort by. A deterministic sort is required for paging to be consistent."
    • addedInput schema / properties / sortfield / type
      Added value: +"string"
  3. First observedv0.5.3

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds useful domain context about what network discovery rules do, but it does not disclose behavioral details such as pagination behavior, permissions, or response characteristics beyond what the schema provides.

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?

The description is short and front-loads the core action. The second sentence about network scanning is useful domain context, though not strictly required for selecting or invoking 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?

Given that annotations cover safety and an output schema exists, the description is adequate for understanding the resource. However, it lacks guidance on alternatives such as 'discoveryrule_get' and does not explain when filtering or paging should be used, leaving some context gaps.

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 high at 89%, so the schema already documents most parameters well. The description adds no parameter-specific meaning or syntax, which is acceptable given the strong schema coverage but does not raise it above the baseline.

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: 'Get network discovery rules from Zabbix,' and clarifies that 'drule' means network discovery rules. It explains the domain well, but it does not distinguish this tool from the sibling 'discoveryrule_get,' which appears closely related.

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 gives no guidance on when to use this tool versus alternatives, nor does it mention prerequisites, filtering use cases, or any when-not-to-use conditions. It only implies usage by saying it retrieves network discovery rules.

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