Skip to main content
Glama
mhajder

Zabbix MCP Server

by mhajder

drule_get

Read-onlyIdempotent

Retrieve network discovery rules that scan CIDR ranges for active devices, open ports, and services.

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return. Default is 100.
offsetNoNumber of results to skip (for pagination). Requires sortfield to be set.
outputNoextend
searchNoDictionary with search criteria like {'name': 'LAN'}.
druleidsNoList of network discovery rule IDs to get. If empty, returns all rules.
sortfieldNoField to sort by.
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

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive. Description adds context about the rules' purpose but no additional behavioral traits 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.

Conciseness5/5

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

Two sentences front-loaded with purpose and functionality. No fluff, every sentence adds value.

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?

Given output schema and annotations, description is sufficient for a simple read tool. Could mention that it returns a list, but overall adequate.

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 coverage is high (89%), and description does not discuss parameters. It relies on schema for parameter meaning, providing no extra value.

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 clearly states it gets network discovery rules and explains what those rules are, distinguishing from sibling tools like 'discoveryrule_get' implicitly. However, it does not explicitly differentiate.

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?

No explicit guidance on when to use this tool vs. alternatives. The context is clear for retrieving network discovery rules, but no exclusions or alternatives mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mhajder/zabbix-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server