Skip to main content
Glama
Sign In
Zabbix MCP Server

Zabbix MCP Server

by initMAX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

hanode_get

Read-only

Retrieve Zabbix High Availability cluster nodes to monitor each node's status, address, last access time, and role (active, standby, stopped, or unavailable).

Instructions

Retrieve Zabbix server High Availability (HA) cluster nodes. Returns information about each node's status, address, last access time, and role (active / standby / stopped / unavailable). Use this to monitor the health of a Zabbix HA cluster. This is a read-only method; HA nodes are managed by the Zabbix server process, not via the API.

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]}. Only these keys are accepted: name, address, status. Text properties cannot be filtered; use 'search' for them.
outputNoProperties of the hanode object to return. Pass 'extend' for all, 'count' for the number of matches only, or a list of property names. Default when omitted: ha_nodeid, name, status, address. Properties: address, ha_nodeid, lastaccess, name, port, status.
serverNoTarget Zabbix server. Available: default. Defaults to 'default' if omitted.
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.
sortfieldNoSort by one or more of: name, lastaccess, status (a list for several; pair with 'sortorder'). No other property is sortable.
sortorderNoSort order: 'ASC' (ascending) or 'DESC' (descending).
ha_nodeidsNoReturn only HA nodes with the given IDs.
countOutputNoReturn the count of matching results instead of the actual data.
extra_paramsNoOther native hanode.get parameters, merged into the request as-is. hanode.get has no parameters beyond the typed ones. 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 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": [
+        "preservekeys"
+      ]
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / filter / anyOf
      Previous value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "propertyNames": {
+      "enum": [
+        "name",
+        "address",
+        "status"
+      ]
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / output / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "extend",
+      "count"
+    ],
+    "type": "string"
+  },
+  {
+    "items": {
+      "enum": [
+        "address",
+        "ha_nodeid",
+        "lastaccess",
+        "name",
+        "port",
+        "status"
+      ],
+      "type": "string"
+    },
+    "minItems": 1,
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / output / description
      Previous value: -"Properties of the hanode 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: ha_nodeid, name, status, address. Properties: address, ha_nodeid, lastaccess, name, port, status."New value: +"Properties of the hanode object to return. Pass 'extend' for all, 'count' for the number of matches only, or a list of property names. Default when omitted: ha_nodeid, name, status, address. Properties: address, ha_nodeid, lastaccess, name, port, status."
    • changedInput schema / properties / sortfield / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "name",
+      "lastaccess",
+      "status"
+    ],
+    "type": "string"
+  },
+  {
+    "items": {
+      "enum": [
+        "name",
+        "lastaccess",
+        "status"
+      ],
+      "type": "string"
+    },
+    "minItems": 1,
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / sortfield / description
      Previous value: -"Sort by one or more of: name, lastaccess, status (comma-separated for several; pair with 'sortorder'). No other property is sortable."New value: +"Sort by one or more of: name, lastaccess, status (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": "hanode_getOutput",
-  "type": "object"
-}New value: +null
  2. First observedv1.41.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false; the description reinforces this and adds the non-obvious fact that node lifecycle cannot be changed through the API, which is real context beyond the structured fields. It omits pagination/limit behavior for large clusters, which would have made it a 5.

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 front-loaded sentences with zero filler: purpose, return shape, and the usage/read-only caveat in that order. The enumeration of role values earns its place by telling the agent what status strings to expect.

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?

For a 10-parameter, zero-required read tool with no output schema, the description covers what the tool is and what it returns; the per-parameter semantics (limit, sortfield, output projection, raw_json policy) are fully carried by the schema. Only the absence of any mention of result limits or default output selection keeps it from a 5.

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% and the schema is unusually rich (filter keys, sortable fields, output projection, the raw_json policy warning are all documented inline). The description adds no parameter-level detail beyond restating the returned properties, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Retrieve Zabbix server High Availability (HA) cluster nodes') and enumerates the returned fields, including the role enum values (active / standby / stopped / unavailable). No sibling tool covers HA nodes, so an agent can distinguish it immediately from the many other *_get tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit use case ('Use this to monitor the health of a Zabbix HA cluster') and a clear when-not boundary: HA nodes are managed by the Zabbix server process, not via the API, so no write path exists here. It does not name a sibling alternative, but for a unique resource type there is none.

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

Deploy Server

Other Tools