Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

Item Get

item_get
Read-onlyIdempotent

Retrieves Zabbix items (metrics) and their definitions, with filters for hosts, templates, names, and keys plus paging options.

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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "item_get"
  }
}

Input 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. An empty list matches none.
itemidsNoList of item IDs to get. Omit to return all items; an empty list matches none.
groupidsNoList of group IDs to get items from hosts in those groups. An empty list matches none.
webitemsNoIf true, also return web scenario items (webitems=true), which Zabbix leaves out by default.
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. An empty list matches none.
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

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.7.1
    • changedInput schema / properties / groupids / description
      Previous value: -"List of group IDs to get items from hosts in those groups."New value: +"List of group IDs to get items from hosts in those groups. An empty list matches none."
    • changedInput schema / properties / hostids / description
      Previous value: -"List of host IDs to get items from. Filters items by host."New value: +"List of host IDs to get items from. Filters items by host. An empty list matches none."
    • changedInput schema / properties / itemids / description
      Previous value: -"List of item IDs to get. If empty, returns all items."New value: +"List of item IDs to get. Omit to return all items; an empty list matches none."
    • changedInput schema / properties / templateids / description
      Previous value: -"List of template IDs to get items from those templates."New value: +"List of template IDs to get items from those templates. An empty list matches none."
    • addedInput schema / properties / webitems
      Added value: +{
      +  "default": false,
      +  "description": "If true, also return web scenario items (webitems=true), which Zabbix leaves out by default.",
      +  "type": "boolean"
      +}
  2. 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"
  3. First observedv0.5.3

TDQS

B3.2/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, so the safety profile is clear. The description adds domain context that items define collected metrics and produce value streams, but it does not add operational behavior such as pagination, permissions, or response effects. With annotations carrying the safety signal, this is adequate 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is front-loaded with the purpose in the first sentence and then uses two short sentences to define items. It is appropriately sized and has little waste. The extra definitional context is useful but not strictly essential.

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?

The tool has 18 parameters, but 94% schema coverage and an output schema mean the description does not need to explain parameters or return values. Annotations cover the read-only/idempotent safety profile. The missing piece is explicit guidance on when to use this tool versus related read tools such as history_get or trend_get.

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%, so the 18 parameters are already well documented in the schema. The description adds no parameter-specific meaning beyond the schema. A baseline 3 is appropriate when the schema does nearly all parameter explanation.

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 first sentence states a specific read verb and resource: 'Get items (metrics) from Zabbix.' The follow-up explains what items are, which helps distinguish this data-source resource from adjacent tools. However, it does not explicitly contrast with siblings such as itemprototype_get or item_update/create/delete.

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?

The description gives no explicit when-to-use guidance or alternatives. It never says when to choose item_get over history_get, trend_get, or itemprototype_get, nor when not to use it. Usage is only implied by the verb 'Get'.

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