Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

dcheck_get

Read-only

Retrieve discovery checks defined within Zabbix network discovery rules to inspect SNMP, agent, ICMP, or TCP tests and filter results by rule or check ID.

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

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 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 (a list 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, groupCount, limitSelects. Switches (true turns one on, false is the same as leaving it out): groupCount. groupCount goes with output='count': the count is then split by the ID filters the method groups by (hostids, groupids ...), one row per ID with 'rowscount'; a single row without such a filter. 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv1.42.2
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / extra_params / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "propertyNames": {
      +      "enum": [
      +        "editable",
      +        "excludeSearch",
      +        "preservekeys",
      +        "startSearch",
      +        "dserviceids",
      +        "groupCount",
      +        "limitSelects",
      +        "selectDRules"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / extra_params / description
      Previous value: -"Other 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."New value: +"Other native dcheck.get parameters, merged into the request as-is. Parameters: dserviceids, groupCount, limitSelects. Switches (true turns one on, false is the same as leaving it out): groupCount. groupCount goes with output='count': the count is then split by the ID filters the method groups by (hostids, groupids ...), one row per ID with 'rowscount'; a single row without such a filter. 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."
    • changedInput schema / properties / filter / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "propertyNames": {
      +      "enum": [
      +        "allow_redirect",
      +        "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"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / output / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "extend",
      +      "count"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "allow_redirect",
      +        "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"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / output / description
      Previous value: -"Properties 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."New value: +"Properties of the dcheck object to return. Pass 'extend' for all, 'count' for the number of matches only, or a 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."
    • changedInput schema / properties / search / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "propertyNames": {
      +      "enum": [
      +        "key_",
      +        "ports",
      +        "snmp_community",
      +        "snmpv3_authpassphrase",
      +        "snmpv3_contextname",
      +        "snmpv3_privpassphrase",
      +        "snmpv3_securityname"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / sortfield / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "dcheckid",
      +      "druleid"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "dcheckid",
      +        "druleid"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / sortfield / description
      Previous value: -"Sort by one or more of: dcheckid, druleid (comma-separated for several; pair with 'sortorder'). No other property is sortable."New value: +"Sort by one or more of: dcheckid, druleid (a list for several; pair with 'sortorder'). No other property is sortable."
    • changedInput schema / properties / sortorder / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "ASC",
      +      "DESC"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "ASC",
      +        "DESC"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "result": {
      -      "title": "Result",
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "result"
      -  ],
      -  "title": "dcheck_getOutput",
      -  "type": "object"
      -}New value: +null
  2. First observedv1.41.0

TDQS

B3.1/5.0
Behavior2/5

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

The only behavioral claim, '(read-only)', simply restates readOnlyHint=true from the annotations, so it earns no credit. With safety already covered structurally, the description adds no behavior an agent would need: nothing on result limits/pagination, the default three-property projection when `output` is omitted, or that untrusted Zabbix data comes back prompt-injection-wrapped unless raw_json is set.

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, front-loaded with the action and scope, then immediately defining the resource. No filler, no repetition, and the most important disambiguating fact (checks live inside rules) is stated early.

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?

For a read-only list tool with a fully documented 14-parameter schema and readOnlyHint annotations, the description is minimally sufficient: an agent knows what it fetches. However, with no output schema present, the description never indicates what a returned check looks like or that output defaults to a three-property projection unless 'extend' is requested.

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, including filter keys, output projections, extra_params validation and the raw_json security warning, so the schema does the heavy lifting. The description adds no parameter meaning beyond the schema, making the baseline 3 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?

States a specific verb ('Retrieve') and resource ('discovery checks') and then defines the resource domain-specifically as the individual tests (SNMP, agent, ICMP ping, TCP port) inside a discovery rule. It implicitly distinguishes itself from the sibling drule_get by explaining that rules *contain* checks, but never names that sibling or states the routing explicitly.

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?

There is no explicit when-to-use guidance and no exclusions. An agent must infer from the definition alone that this is for reading check definitions rather than rule definitions (drule_get) or discovered hosts/services (dhost_get, dservice_get), all of which appear as siblings.

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