Skip to main content
Glama
initMAX

Zabbix MCP Server

dcheck_get

Read-only

Retrieve read-only discovery checks defined in Zabbix network discovery rules, including SNMP, agent, ICMP ping, and TCP port tests.

Instructions

Retrieve discovery checks (read-only). Discovery checks are the individual tests (SNMP, agent, ICMP ping, TCP port, etc.) defined within a network discovery rule. Each discovery rule contains one or more checks.

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_redirect (7.0+), dcheckid, druleid, host_source, key_, name_source, ports, snmp_community, snmpv3_authpassphrase, snmpv3_authprotocol, snmpv3_contextname, snmpv3_privpassphrase, snmpv3_privprotocol, snmpv3_securitylevel, snmpv3_securityname, type, uniq. Text properties cannot be filtered; use 'search' for them.
outputNoProperties of the dcheck 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: dcheckid, druleid, type. Properties: allow_redirect (7.0+), dcheckid, druleid, host_source, key_, name_source, ports, snmp_community, snmpv3_authpassphrase, snmpv3_authprotocol, snmpv3_contextname, snmpv3_privpassphrase, snmpv3_privprotocol, snmpv3_securitylevel, snmpv3_securityname, type, uniq.
searchNoReturn results whose string properties contain the given pattern (case-insensitive; '*' is a wildcard when searchWildcardsEnabled is true). Example: {"name": "web"}. Keys: key_, ports, snmp_community, snmpv3_authpassphrase, snmpv3_contextname, snmpv3_privpassphrase, snmpv3_securityname.
serverNoTarget Zabbix server. Available: default. Defaults to 'default' if omitted.
druleidsNoReturn only discovery checks belonging to the given network discovery rules.
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.
dcheckidsNoReturn only discovery checks with the given IDs.
sortfieldNoSort by one or more of: dcheckid, druleid (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 dcheck.get parameters, merged into the request as-is. Parameters: dserviceids. Sub-object selects (value 'extend', 'count' or a list of property names): selectDRules (6.0+). 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.4/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, and the description's '(read-only)' merely restates that. It adds useful domain context (dchecks are individual tests within a discovery rule) but says nothing about pagination, rate limits, or the security-preamble behavior that the raw_json parameter implies. Reasonable given annotations carry the safety profile, but not rich.

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?

Three short sentences with the core purpose front-loaded, zero filler, and the domain explanation placed immediately after the action so an agent gets context without wading through noise.

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 a rich input schema, an existing output schema, and annotations covering the read-only nature, the description is largely complete for calling the tool. The only real omission is routing guidance against the many sibling *_get tools, which is minor here.

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 all 14 parameters, so the schema fully documents limit, filter, output, search, sortfield, and the rest. The description contributes no additional parameter meaning, 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?

States a specific verb ('Retrieve') and resource ('discovery checks'), and the second and third sentences define what a dcheck is and its relationship to a discovery rule, which meaningfully distinguishes it from siblings like drule_get and discoveryrule_get. It stops short of explicitly naming the sibling it is not, so it lands just below a 5.

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 offers no when-to-use or when-not-to-use guidance and names no alternative tool, despite many similar *_get siblings (drule_get, discoveryrule_get, dservice_get). Usage is only implied by the purpose statement, leaving the agent to infer routing on its own.

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