Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

Itemprototype Get

itemprototype_get
Read-onlyIdempotent

Fetch item prototypes from Zabbix to examine template items generated by discovery rules. Use filters for hosts, items, or discovery rules; supports paging and sorting.

Instructions

Get item prototypes from Zabbix.

Item prototypes are template items created by discovery rules that generate actual items dynamically based on discovered entities.

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": "itemprototype_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'}.
hostidsNoList of host IDs to get item prototypes from. An empty list matches none.
itemidsNoList of item prototype IDs to get. An empty list matches none.
sortfieldNoField to sort by. A deterministic sort is required for paging to be consistent.itemid
sortorderNoSort direction - 'ASC' or 'DESC'.ASC
count_outputNoIf true, returns only the count of matched objects as an integer.
discoveryidsNoList of discovery rule IDs to get prototypes from. An empty list matches none.
filter_paramsNoAdditional filter parameters for advanced filtering.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.7.1
    • changedInput schema / properties / discoveryids / description
      Previous value: -"List of discovery rule IDs to get prototypes from."New value: +"List of discovery rule IDs to get prototypes from. An empty list matches none."
    • changedInput schema / properties / hostids / description
      Previous value: -"List of host IDs to get item prototypes from."New value: +"List of host IDs to get item prototypes from. An empty list matches none."
    • changedInput schema / properties / itemids / description
      Previous value: -"List of item prototype IDs to get."New value: +"List of item prototype IDs to get. An empty list matches none."
  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, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds useful domain context (what a prototype is and how it is produced) but says nothing about pagination behavior, the count_output mode, or result size limits that the schema hints at.

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?

Two short sentences, front-loaded with the action, and no filler. The second sentence earns its place by disambiguating the domain term, though it is arguably the only thing beyond the name.

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?

With an output schema present and annotations covering safety, the description need not explain return values. But for an 11-parameter, filter-heavy list tool it omits any mention of filtering capabilities, deterministic sorting for paging, or the count-only mode, leaving a gap the schema only partially fills.

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 91%, so nearly all 11 parameters are documented inline (limit/offset paging, hostids, itemids, discoveryids, count_output, sortfield). The description adds no parameter-level meaning beyond the schema, which is the correct baseline behavior here.

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?

States a specific verb and resource ("Get item prototypes from Zabbix") and even explains the domain concept (template items generated by discovery rules). However, it never distinguishes itself from close siblings like item_get or discoveryrule_get, so the agent must infer the boundary.

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?

There is no explicit guidance on when to call this versus item_get, discoveryrule_get, or template_get. The only hint is the conceptual note that prototypes come from discovery rules, which implies usage but never states a selection condition or exclusion.

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