Skip to main content
Glama
mhajder

Zabbix MCP Server

by mhajder

host_get

Read-onlyIdempotent

Retrieve monitored hosts from Zabbix with filters for IDs, groups, templates, proxies, or search criteria to find specific hosts in your monitoring system.

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.

Input Schema

TableJSON 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.
groupidsNoList of host group IDs to filter by.
proxyidsNoList of proxy IDs to filter by.
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.
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

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 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"
  2. First observedv0.5.3

TDQS

A3.8/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, covering safety. The description adds minor context (list of hosts, filtering) but does not disclose pagination behavior, response shape, or any performance implications. With annotations covering the core safety profile, this is acceptable but not rich.

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?

The description is concise, with the main action in the first sentence and supporting detail in the second. It is front-loaded, free of fluff, and every sentence contributes to understanding. It does not repeat schema information unnecessarily.

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?

Given 18 parameters and a fully documented schema, the description covers the core functionality and typical use case. It does not explain every parameter (which the schema already does) but provides enough context for an agent to decide when to invoke the tool. The missing pagination detail is present in the offset parameter description.

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?

The input schema provides 100% parameter coverage with detailed descriptions for all 18 parameters. The tool description merely lists the filter categories (IDs, groups, templates, proxies, search) without adding new meaning beyond the schema. Since schema coverage is high, 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?

The description clearly states a specific verb ('Get') and resource ('hosts from Zabbix'), and explicitly mentions optional filtering by various criteria. This distinguishes it from sibling tools like hostgroup_get or template_get, which target different resources. The purpose is unambiguous.

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?

The description implies when to use it ('useful for discovering which hosts are available'), but does not explicitly contrast it with sibling getter tools or state when not to use it. The agent could benefit from a note like 'to filter by host groups, use hostgroup_get instead.' No exclusion or alternative is given.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mhajder/zabbix-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server