Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

Item Create

item_create

Creates a new Zabbix item to define what metric a host collects, including item type, key, update interval, and value type.

Instructions

Create a new item in Zabbix.

Items define what data is collected from a host. Each item specifies the metric name, how to collect it (agent, SNMP, etc.), what interval to use, and what data type to store.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "key_": "<key_>",
      "hostid": "<hostid>",
      "type_": "<type_>",
      "value_type": "<value_type>"
    },
    "name": "item_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
key_YesItem key.
nameYesItem name.
delayNoUpdate interval. Must be '0' for trapper (2) and dependent (18) items.1m
type_YesItem type (0=Zabbix agent, 2=trapper, etc.).
unitsNoOptional units for the values like 'bytes', 'CPU%', 'rpm'.
hostidYesHost ID.
value_typeYesValue type (0=float, 1=char, 2=log, 3=unsigned, 4=text).
descriptionNoOptional item description explaining its purpose.
interfaceidNoHost interface to poll through. Required for Zabbix agent (0), SNMP agent (20), SNMP trap (17), IPMI (12) and JMX (16) items on a host.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.7.1
    • changedInput schema / properties / value_type / description
      Previous value: -"Value type (0=float, 1=char, 3=unsigned, 4=text)."New value: +"Value type (0=float, 1=char, 2=log, 3=unsigned, 4=text)."
  2. Changed2 schema fields changedv0.6.0
    • changedInput schema / properties / delay / description
      Previous value: -"Collection interval. Default '1m'. Use time suffixes like '30s', '5m', '1h'."New value: +"Update interval. Must be '0' for trapper (2) and dependent (18) items."
    • addedInput schema / properties / interfaceid
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Host interface to poll through. Required for Zabbix agent (0), SNMP agent (20), SNMP trap (17), IPMI (12) and JMX (16) items on a host."
      +}
  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=false, idempotentHint=false, and destructiveHint=false. The description adds domain context about what an item represents (metric, collection method, interval, data type) but does not disclose creation side effects, uniqueness constraints, required permissions, or failure behavior. With annotations covering the safety profile, this is adequate but incomplete.

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 three sentences and front-loads the action. The item-model explanation is useful and compact, though the latter sentences are more conceptual than invocation-critical.

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?

The tool has 9 parameters, 5 required, with full schema descriptions, annotations, and an output schema, so return values and most parameter detail are covered elsewhere. The description supplies purpose and item-model context, but omits operational prerequisites and sibling-routing guidance, leaving it complete enough but not rich.

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 coverage is 100%, and the schema documents types, defaults, and conditional requirements such as delay=0 for trapper/dependent items and interfaceid being required for certain item types. The description only echoes the high-level fields and adds no syntax or conditional guidance beyond the schema.

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 opens with a specific verb and resource ("Create a new item in Zabbix") and explains what an item is. It does not explicitly differentiate from siblings such as item_update or item_get, so it is clear but lacks sibling-routing language.

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 when-to-use or when-not-to-use guidance, and it never mentions item_update for modifying existing items or prerequisites for creation. Usage is only implied by the verb "Create".

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