Zabbix MCP Server

Overview Schema Source Related Servers Discussions Admin

hanode_get

Read-only

Retrieve Zabbix High Availability cluster nodes and their status, address, last access time, and role to monitor HA cluster health.

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

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of results to return.
`filter`	No	Return 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.
`output`	No	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.
`server`	No	Target Zabbix server. Available: default. Defaults to 'default' if omitted.
`raw_json`	No	Strips 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.
`sortfield`	No	Sort by one or more of: name, lastaccess, status (comma-separated for several; pair with 'sortorder'). No other property is sortable.
`sortorder`	No	Sort order: 'ASC' (ascending) or 'DESC' (descending).
`ha_nodeids`	No	Return only HA nodes with the given IDs.
`countOutput`	No	Return the count of matching results instead of the actual data.
`extra_params`	No	Other 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.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.41.0Oct 20, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces it with a genuinely useful behavioral fact beyond the annotations: HA nodes 'are managed by the Zabbix server process, not via the API,' i.e. there is no write counterpart. It does not mention the raw_json/security-preamble trade-off (covered in the schema) or any rate/cost behavior.

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?

Front-loaded with the core purpose, then return fields, then usage, then a behavioral caveat. Each sentence earns its place, though the enumeration of return fields lightly duplicates what the output schema already lists.

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 an output schema, full annotation coverage, and 100% parameter documentation, the description only needs to carry purpose, usage, and behavioral context — and it does so. Nothing critical is missing, though it could say more about result volume/pagination.

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%, so the schema already documents all ten parameters (limit, filter, output, sort, etc.) in detail. The description adds no parameter-level guidance, which is acceptable but warrants the baseline 3.

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 dimensions (status, address, last access time, role) plus the role enum values. An agent can immediately tell this apart from generic siblings like serverinfo_get or proxy_get.

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?

Explicitly gives the use case: 'Use this to monitor the health of a Zabbix HA cluster.' That is clear context, but no alternatives or when-not conditions are named (e.g., how it relates to serverinfo_get/apm status tools).

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

Deploy Server