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. Use to discover available 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
limitNoMaximum number of results to return. Default is 100.
offsetNoNumber of results to skip (for pagination). Requires sortfield to be set.
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.
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 (selectGroups=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

Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description does not need to reiterate these. The description adds no additional behavioral context beyond what the annotations provide.

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 two sentences, front-loaded with the primary purpose, and contains no unnecessary words. Every sentence adds value.

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 the tool's complexity (18 parameters, extensive filtering), the description provides a good overview of capabilities. The output schema exists, so no need to describe return values. The description covers the essential use case adequately.

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 has 100% description coverage for all 18 parameters. The description adds a high-level summary of filtering options but does not provide meaningful additional semantics beyond the schema.

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 the tool retrieves hosts from Zabbix with optional filtering. It distinguishes from sibling mutation tools like host_create and host_delete by being a read operation.

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?

The description explains it is useful for discovering hosts available in the monitoring system and lists filtering options. However, it does not explicitly state when not to use it or mention alternative tools for specific host-related queries.

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

Install Server

Other Tools

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