Skip to main content
Glama
mhajder

Zabbix MCP Server

by mhajder

item_get

Read-onlyIdempotent

Retrieve monitoring metrics from Zabbix by filtering on hosts, groups, templates, or search criteria. Returns item details and optionally associated hosts, tags, or triggers.

Instructions

Get items (metrics) from Zabbix.

Items are the data sources in Zabbix - they define what metrics are collected and how (protocol, interval, etc.). Each item produces a stream of values over time.

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.
outputNoextend
searchNoDictionary with search criteria like {'name': 'CPU'} for substring matching.
hostidsNoList of host IDs to get items from. Filters items by host.
itemidsNoList of item IDs to get. If empty, returns all items.
groupidsNoList of group IDs to get items from hosts in those groups.
sortfieldNoField to sort by.
sortorderNoSort direction - 'ASC' or 'DESC'.ASC
select_tagsNoIf true, include the tags for each item in the response (selectTags=extend).
templateidsNoList of template IDs to get items from those templates.
count_outputNoIf true, returns only the count of matched objects as an integer.
select_hostsNoIf true, include the hosts each item belongs to in the response (selectHosts=extend).
filter_paramsNoAdditional filter parameters for advanced filtering.
select_triggersNoIf true, include the triggers for each item in the response (selectTriggers=extend).
item_key_containsNoShortcut to search for items by key (constructs search={'key_': item_key_contains}).
item_name_containsNoShortcut to search for items by name (constructs search={'name': item_name_contains}).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the description need not repeat these. It adds value by explaining that items are data sources producing values over time, which is helpful context beyond the annotations.

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?

The description is concise (two sentences) and front-loaded with the primary action. Every sentence adds value, though a bit more structure could improve clarity.

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?

Given the output schema exists and annotations cover safety, the description provides domain context but lacks guidance on filtering or pagination patterns. It is adequate but not comprehensive for a tool with 17 parameters.

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 94% coverage, meaning parameters are well-documented. The description adds no parameter-specific details beyond the schema, so baseline score of 3 is appropriate.

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 description clearly states 'Get items (metrics) from Zabbix' and explains what items are. It specifies the verb and resource, but does not explicitly distinguish from sibling tools like host_get or history_get, though the focus on items is clear.

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?

No explicit guidance on when to use this tool versus alternatives. The description does not mention when-not to use or suggest other tools for different queries, leaving the agent to infer usage context.

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