Skip to main content
Glama
leroylim

Zabbix MCP Server

by leroylim

zabbix_host_get

Retrieve Zabbix hosts by ID, name, or IP, with filters for groups, templates, and custom criteria. Optionally include related data such as interfaces, triggers, macros, and inventory.

Instructions

Retrieves Zabbix host information. Can filter by various criteria including direct IDs or by resolving host identifiers (names, IPs).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of hosts to return.
filterNoFilter criteria (e.g., { status: 0, host: 'webserver01' }).
outputNoProperties to return. Defaults to 'extend'. Common options: ['hostid', 'host', 'name', 'status', 'error', 'available'].extend
searchNoWildcard search criteria (e.g., { host: 'web*' }). Will search in 'host' (technical name) and 'name' (visible name) fields primarily.
hostidsNoArray of direct Zabbix Host IDs to retrieve.
groupidsNoArray of group IDs to filter hosts by.
sortfieldNoField(s) to sort by (e.g., 'name', ['status', 'host']).
sortorderNoSort order ('ASC' or 'DESC').
selectItemsNoInclude items from the host.
templateidsNoArray of template IDs to filter hosts by.
selectGroupsNoInclude host group information. Use 'extend' for all group fields or specify an array like ['groupid', 'name'].extend
selectMacrosNoInclude host macros. Use 'extend' for all macro fields or specify an array like ['macro', 'value'].
selectTriggersNoInclude triggers from the host.
hostIdentifiersNoArray of host technical names, visible names, or IP addresses to resolve to IDs for filtering. Use this OR direct filter options like 'hostids' or 'filter'.
selectInventoryNoInclude host inventory data. Use 'extend' for all inventory fields or specify an array of inventory property names (e.g. ['os', 'type']).
selectInterfacesNoInclude host interface information. Use 'extend' for all interface fields or specify an array like ['interfaceid', 'ip', 'port', 'type'].extend
selectParentTemplatesNoInclude linked parent template information. Use 'extend' for all template fields or specify an array like ['templateid', 'name'].extend
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It communicates a read-only operation ('Retrieves') and a useful behavior (resolving host identifiers), but does not detail return format, pagination, defaults, or potential limitations. This adds some context but leaves gaps for a 17-parameter tool.

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 with no fluff, front-loaded with the core purpose. Every word earns its place, effectively balancing brevity with the key filtering capability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (17 parameters, nested objects) and lack of output schema, the description is insufficiently complete. It does not explain what the return data looks like, when to prefer this over related getters, or any edge cases. The schema covers parameter syntax but the description lacks broader operational context.

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 baseline is 3. The description mentions 'resolving host identifiers', which aligns with the hostIdentifiers parameter, but this is a high-level summary rather than adding new parameter-specific meaning. The schema already documents each parameter thoroughly.

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 'Retrieves Zabbix host information' with a specific verb and resource, and distinguishes it from sibling tools like zabbix_host_create or zabbix_get_items by focusing on hosts. It further clarifies scope by mentioning filtering by direct IDs or resolving host identifiers.

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 provides clear usage context by mentioning the ability to filter by various criteria, including direct IDs or resolving host identifiers. However, it does not explicitly exclude alternatives like zabbix_get_discovered_hosts or other getter tools, though the focus on 'host information' makes its primary use evident.

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/leroylim/zabbix-mcp-server-nodejs'

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