Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

Host Get

host_get
Read-onlyIdempotent

Retrieves monitored hosts from Zabbix and filters them by IDs, groups, templates, proxies, status, or search criteria to discover available hosts.

Instructions

Get hosts from Zabbix with optional filtering.

Retrieves a list of monitored hosts from Zabbix. You can filter by host IDs, groups, templates, proxies, or use search criteria. This is useful for discovering which hosts are available in your monitoring system.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "host_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPage size - maximum number of results to return. Default is 100.
offsetNoNumber of matching hosts to skip. Use with 'limit' to page through results; check 'has_more' and 'total' in the response.
outputNoOutput format: 'extend' or specific fields.extend
searchNoSearch criteria (e.g., {'host': 'web'} to perform a 'LIKE' search).
statusNoShortcut to filter by status (0=enabled, 1=disabled) (constructs filter={'status': status}).
hostidsNoList of host IDs to retrieve. An empty list matches none.
groupidsNoList of host group IDs to filter by. An empty list matches none.
proxyidsNoList of proxy IDs to filter by. An empty list matches none.
sortfieldNoField to sort by - 'hostid', 'host', 'name' or 'status'. A deterministic sort is required for paging to be consistent.hostid
sortorderNoSort direction - 'ASC' or 'DESC'.ASC
select_tagsNoIf true, include the tags for each host in the response (selectTags=extend).
templateidsNoList of template IDs to filter by. An empty list matches none.
count_outputNoIf true, returns only the count of matched objects as an integer.
filter_paramsNoFilter criteria (e.g., {'status': 0}).
select_groupsNoIf true, include the host groups each host belongs to in the response (selectHostGroups=extend).
select_templatesNoIf true, include the templates linked to each host in the response (selectTemplates=extend).
hostname_containsNoShortcut to search for hosts by name (constructs search={'host': hostname_contains}).
select_interfacesNoIf true, include the interfaces for each host in the response (selectInterfaces=extend).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.7.1
    • changedInput schema / properties / groupids / description
      Previous value: -"List of host group IDs to filter by."New value: +"List of host group IDs to filter by. An empty list matches none."
    • changedInput schema / properties / hostids / description
      Previous value: -"List of host IDs to retrieve."New value: +"List of host IDs to retrieve. An empty list matches none."
    • changedInput schema / properties / proxyids / description
      Previous value: -"List of proxy IDs to filter by."New value: +"List of proxy IDs to filter by. An empty list matches none."
    • changedInput schema / properties / templateids / description
      Previous value: -"List of template IDs to filter by."New value: +"List of template IDs to filter by. An empty list matches none."
  2. Changed7 schema fields changedv0.6.0
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of results to return. Default is 100."New value: +"Page size - maximum number of results to return. Default is 100."
    • changedInput schema / properties / offset / description
      Previous value: -"Number of results to skip (for pagination). Requires sortfield to be set."New value: +"Number of matching hosts to skip. Use with 'limit' to page through results; check 'has_more' and 'total' in the response."
    • changedInput schema / properties / select_groups / description
      Previous value: -"If true, include the host groups each host belongs to in the response (selectGroups=extend)."New value: +"If true, include the host groups each host belongs to in the response (selectHostGroups=extend)."
    • removedInput schema / properties / sortfield / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • changedInput schema / properties / sortfield / default
      Previous value: -nullNew value: +"hostid"
    • changedInput schema / properties / sortfield / description
      Previous value: -"Field to sort by."New value: +"Field to sort by - 'hostid', 'host', 'name' or 'status'. A deterministic sort is required for paging to be consistent."
    • addedInput schema / properties / sortfield / type
      Added value: +"string"
  3. First observedv0.5.3

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds that filtering is optional and that it returns a list, but says nothing about default paging behavior (limit=100), the has_more/total response fields it enables, or that count_output switches to a scalar return — all left to the schema.

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?

Three short sentences, front-loaded with the verb and resource. Minor waste: the first and second sentences largely restate each other ('Get hosts from Zabbix' / 'Retrieves a list of monitored hosts from Zabbix').

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 18 fully documented parameters, an output schema, and complete annotations, the description only needs to frame the tool's role — which it does. It omits any mention of paging strategy or response-expansion flags, but those are well covered elsewhere, so the gap is small.

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 baseline is 3. The description restates the filter dimensions (host IDs, groups, templates, proxies, search) that already appear as schema properties but adds no semantics of its own — e.g., that an empty ID list matches nothing, or that a deterministic sortfield is required for stable paging.

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 ('Get') and resource ('hosts from Zabbix') and names the filterable dimensions. It is clear what the tool returns (a list of monitored hosts), but it never distinguishes itself from siblings like hostgroup_get or template_get beyond the resource noun.

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

Usage Guidelines3/5

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

'This is useful for discovering which hosts are available in your monitoring system' is an implied usage context rather than explicit guidance. No when-not-to-use cases and no named alternative (e.g., that mutations belong to host_create/host_update) are given, though the read-only nature of the operation makes the choice fairly obvious.

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