Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

Item Update

item_update

Modify properties of an existing Zabbix monitoring item, such as its name, collection interval, units, description, or status. Specify only the fields you want to change.

Instructions

Update an existing item in Zabbix.

Modifies properties of an existing monitoring item. You can change the name, collection interval, units, or status. Only specify the fields you want to change.

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": {
      "itemid": "<itemid>"
    },
    "name": "item_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew item name.
delayNoNew collection interval (e.g., '30s', '5m', '1h').
unitsNoNew units for the values.
itemidYesID of the item to update.
statusNo0=enabled, 1=disabled.
descriptionNoNew description.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.3

TDQS

A3.5/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, so the safety profile is covered. The description adds that only supplied fields are changed, but is silent on permissions, what happens to omitted/null fields, and failure behavior for non-existent items. No contradiction with 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?

Front-loaded with the action, then scope, then the key partial-update rule. Slightly redundant: 'Modifies properties of an existing monitoring item' restates the opening sentence without adding information.

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?

A 6-parameter mutation tool with full schema coverage, an output schema, and annotations covering the safety profile. The description is adequate; the only minor gap is that omitted-field behavior and permissions are left implicit.

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 100%, so each of the 6 parameters is already documented. The description echoes four of them (name, interval, units, status) without adding format or constraint detail beyond the schema (e.g., delay syntax '30s'/'5m' comes from the schema, not the description). Baseline 3 applies.

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 ('Update an existing item in Zabbix') and clarifies it modifies properties of an existing monitoring item rather than creating one. The verb alone distinguishes it from item_create/item_delete/item_get siblings, but no sibling is named explicitly.

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?

'Only specify the fields you want to change' gives useful partial-update guidance and implies the item must already exist. However, it never states prerequisites (permissions, item lifecycle state) or when to prefer item_create versus this tool.

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