Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

Trigger Update

trigger_update

Modify an existing Zabbix trigger's expression, severity, status, description, or comments while leaving unspecified fields unchanged.

Instructions

Update an existing trigger in Zabbix.

Modifies properties of an existing trigger. You can change the description, expression, priority, status, or comments. Only specify 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": {
      "triggerid": "<triggerid>"
    },
    "name": "trigger_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNo0=enabled, 1=disabled.
commentsNoNew comments/notes.
priorityNoNew severity level (0-5).
triggeridYesID of the trigger to update.
expressionNoNew trigger expression.
descriptionNoNew trigger name/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?

The description adds partial-update semantics ('only specify fields you want to change'), which is useful beyond the annotations. However, with readOnlyHint=false and idempotentHint=false, it does not disclose whether changes take effect immediately, permission requirements, or what happens if no fields are supplied.

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 short and front-loaded, with the partial-update rule at the end. The first two sentences are somewhat redundant ('Update an existing trigger' / 'Modifies properties of an existing trigger'), but there is no significant waste.

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 output schema exists, the rich parameter descriptions, and the annotations, the description is nearly complete for a partial-update tool. It could be stronger by mentioning required triggerid or side effects, but the essential call semantics are present.

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 the baseline is 3. The description lists the changeable fields (description, expression, priority, status, comments) and reinforces that only desired fields should be sent, but it adds no per-parameter detail 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 gives a specific verb and resource ('Update an existing trigger in Zabbix') and clarifies scope with 'Modifies properties of an existing trigger.' It implicitly distinguishes update from sibling trigger_create/trigger_get/trigger_delete, but never explicitly names or contrasts those siblings.

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 phrase 'Only specify fields you want to change' gives useful guidance for partial updates, but the description does not explicitly say when to use this tool versus trigger_create, trigger_get, or trigger_delete.

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