Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

Discoveryrule Get

discoveryrule_get
Read-onlyIdempotent

Retrieve discovery rules from Zabbix to inspect or filter automated network discovery settings, helping manage dynamic host and item detection without manual configuration.

Instructions

Get discovery rules from Zabbix.

Discovery rules automatically detect items, triggers, and interfaces from network resources. They enable dynamic host and item management without manual configuration.

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": "discoveryrule_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': 'SNMP'}.
hostidsNoList of host IDs to get discovery rules from. An empty list matches none.
itemidsNoList of item IDs (discovery rules are items) to get. An empty list matches none.
sortfieldNoField to sort by. A deterministic sort is required for paging to be consistent.itemid
sortorderNoSort direction - 'ASC' or 'DESC'.ASC
templateidsNoList of template IDs to get discovery rules from. An empty list matches none.
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. Changed3 schema fields changedv0.7.1
    • changedInput schema / properties / hostids / description
      Previous value: -"List of host IDs to get discovery rules from."New value: +"List of host IDs to get discovery rules from. An empty list matches none."
    • changedInput schema / properties / itemids / description
      Previous value: -"List of item IDs (discovery rules are items) to get."New value: +"List of item IDs (discovery rules are items) to get. An empty list matches none."
    • changedInput schema / properties / templateids / description
      Previous value: -"List of template IDs to get discovery rules from."New value: +"List of template IDs to get discovery rules from. 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: +"itemid"
    • 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?

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful domain context about what discovery rules do, but it does not add behavioral details beyond annotations, such as paging, filtering, or response behavior; the output schema covers return values.

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 in the first sentence. The second sentence provides domain background rather than invocation guidance, so it is not maximally efficient, but it is not excessive.

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?

The description, rich schema, annotations, and output schema together make the tool callable. Still, for an 11-parameter list/get tool with a closely related sibling, the missing usage guidance and sibling differentiation leave a meaningful contextual gap.

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 91%, so the schema already documents nearly all 11 parameters. The description adds no parameter-specific semantics, but with such high coverage the baseline of 3 is appropriate.

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 uses a clear verb+resource phrase, 'Get discovery rules from Zabbix,' and explains what discovery rules are. However, it does not distinguish this tool from the similarly named sibling 'drule_get' or clarify when this should be used instead.

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 says what the tool retrieves but provides no explicit when-to-use guidance, no exclusions, and no alternatives. With siblings such as 'drule_get' and 'item_get', an agent is left to infer the correct choice from the name alone.

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