Skip to main content
Glama
initMAX

Zabbix MCP Server

host_get

Read-only

Retrieve Zabbix hosts by ID, host group, proxy, template, or custom filters to inspect and manage monitored servers, VMs, and network devices.

Instructions

Retrieve hosts. Hosts are the core monitored entities in Zabbix - they represent servers, VMs, network devices, or any other resource you monitor. Each host belongs to one or more host groups, can be linked to templates, and contains items, triggers, and graphs that define what is monitored and how.

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: active_available (6.2+), assigned_proxyid (7.0+), auto_compress (removed in 7.0), custom_interfaces, flags, host, hostid, inventory_mode, ipmi_authtype, ipmi_password, ipmi_privilege, ipmi_username, lastaccess (removed in 6.2), maintenance_from, maintenance_status, maintenance_type, maintenanceid, monitored_by (7.0+), name, proxy_address (removed in 7.0), proxy_groupid (7.0+), proxy_hostid (removed in 7.0), proxyid (7.0+), status, templateid, tls_accept, tls_connect, tls_issuer, tls_subject, uuid, vendor_name (6.4+), vendor_version (6.4+), wizard_ready (7.4+). Text properties cannot be filtered; use 'search' for them.
outputNoProperties of the host 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: hostid, host, name, status. Properties: active_available (6.2+), assigned_proxyid (7.0+), auto_compress (removed in 7.0), custom_interfaces, description, flags, host, hostid, inventory_mode, ipmi_authtype, ipmi_password, ipmi_privilege, ipmi_username, lastaccess (removed in 6.2), maintenance_from, maintenance_status, maintenance_type, maintenanceid, monitored_by (7.0+), name, proxy_address (removed in 7.0), proxy_groupid (7.0+), proxy_hostid (removed in 7.0), proxyid (7.0+), readme (7.4+), status, templateid, tls_accept, tls_connect, tls_issuer, tls_psk, tls_psk_identity, tls_subject, uuid, vendor_name (6.4+), vendor_version (6.4+), wizard_ready (7.4+).
searchNoReturn results whose string properties contain the given pattern (case-insensitive; '*' is a wildcard when searchWildcardsEnabled is true). Example: {"name": "web"}. Keys: description, host, ipmi_password, ipmi_username, name, proxy_address (removed in 7.0), readme (7.4+), tls_issuer, tls_subject, uuid, vendor_name (6.4+), vendor_version (6.4+).
serverNoTarget Zabbix server. Available: default. Defaults to 'default' if omitted.
hostidsNoReturn only hosts with the given IDs.
groupidsNoReturn only hosts that belong to the given host groups (by group ID).
proxyidsNoReturn only hosts monitored by the given proxies (by proxy ID).
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: hostid, host, name, status (comma-separated for several; pair with 'sortorder'). No other property is sortable.
sortorderNoSort order: 'ASC' (ascending) or 'DESC' (descending).
with_itemsNoOnly return hosts that have items.
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).
templateidsNoReturn only hosts linked to the given templates (by template ID).
with_graphsNoOnly return hosts that have graphs.
extra_paramsNoOther native host.get parameters, merged into the request as-is. Parameters: dserviceids, evaltype, graphids, httptestids, inheritedTags, interfaceids, itemids, limitSelects, maintenanceids, monitored_hosts, proxy_groupids (7.0+), proxy_hosts (removed in 7.0), searchInventory, severities, tags, templated_hosts, triggerids, withProblemsSuppressed, with_graph_prototypes, with_item_prototypes, with_monitored_httptests, with_monitored_items, with_monitored_triggers, with_simple_graph_item_prototypes, with_simple_graph_items. Sub-object selects (value 'extend', 'count' or a list of property names): selectDashboards (6.0+), selectDiscoveries, selectDiscoveryData (7.4+), selectDiscoveryRule, selectDiscoveryRules (7.4+), selectGraphs, selectGroups (removed in 7.2), selectHostDiscovery, selectHostGroups (6.2+), selectHttpTests, selectInheritedTags, selectInterfaces, selectInventory, selectItems, selectMacros, selectParentTemplates, selectTags, selectTriggers, selectValueMaps (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.
with_triggersNoOnly return hosts that have triggers.
with_httptestsNoOnly return hosts that have web scenarios (HTTP tests).
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

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds no behavioral context of its own - no pagination, default result set, or filtering limits - only a conceptual model of host relationships, which does not describe how the tool behaves.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The action is front-loaded in the first sentence, but the remaining two sentences are background lore about hosts, templates, items and graphs that does not help an agent select or invoke this tool. Reasonably sized but not every sentence earns its place.

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?

With a 20-parameter, 100%-documented schema, an output schema, and read-only annotations, the structured fields carry most of the load. The description is adequate but leaves gaps around when to prefer this over sibling host-related getters, which is the one thing the schema cannot convey.

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 20 parameters, including detailed filter/search/output key lists, so the schema fully documents parameter meaning. The description contributes nothing beyond that, which is the baseline-3 case when the schema does the heavy lifting.

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 first sentence gives a specific verb+resource ('Retrieve hosts') and the following sentences establish what a host is in Zabbix. It is clear what the tool does, but it does not differentiate itself from the many sibling *_get tools (hostgroup_get, hostinterface_get, host_status_get) that an agent must choose between.

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 when-to-use guidance, no stated prerequisites, and no mention of alternatives such as hostgroup_get or host_status_get. The description is domain education about what hosts are rather than instructions on when this retrieval tool is the right choice.

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