Skip to main content
Glama
mhajder

Zabbix MCP Server

by mhajder

item_get

Read-onlyIdempotent

Retrieve Zabbix items (metrics) by host, group, template, or search criteria to examine monitored data sources, collection intervals, and associated 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 matching records to skip. Use with 'limit' to page through results; check 'has_more' and 'total' in the response.
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. A deterministic sort is required for paging to be consistent.itemid
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

Schema Changelog

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

  1. Changed5 schema fields changedv0.6.0
    • changedInput schema / properties / offset / description
      Previous value: -"Number of results to skip (for pagination). Requires sortfield to be set."New value: +"Number of matching records to skip. Use with 'limit' to page through results; check 'has_more' and 'total' in the response."
    • removedInput schema / properties / sortfield / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • changedInput schema / properties / sortfield / default
      Previous value: -nullNew value: +"itemid"
    • changedInput schema / properties / sortfield / description
      Previous value: -"Field to sort by."New value: +"Field to sort by. 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.6/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 the safety profile. The description adds context about items being data sources but does not disclose behavioral traits like pagination behavior, response structure, or any rate limits. Since annotations carry the safety info, the description doesn't contradict them and adds minimal extra behavioral context.

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 three short, well-structured sentences. The core action 'Get items (metrics) from Zabbix' is front-loaded, and the supplementary explanation about items is concise and adds value without padding. No wasted words.

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 presence of a rich output schema (which explains return values), 17 parameters with individual descriptions, and annotations covering safety, the description is sufficient. It correctly conveys that this is a read-only list operation for item definitions, not historical values. Minor gaps like explicit pagination handling are already covered in the offset parameter description, so nothing critical is missing.

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 94% and each parameter (limit, offset, search, hostids, etc.) has a meaningful description in the schema. The tool description itself offers no additional parameter semantics beyond what is already documented, so it neither enhances nor detracts from the schema's clarity. Baseline 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 the action 'Get items (metrics) from Zabbix' with a specific resource and adds context about what items are. It distinguishes from item_create/update/delete by being a getter, but doesn't explicitly differentiate from itemprototype_get, so some ambiguity remains.

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 usage for retrieving item metadata but provides no explicit guidance on when to use this tool vs. item_create, item_update, or itemprototype_get. There is no mention of alternatives or exclusion conditions, leaving the agent to infer context from tool names alone.

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