Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

Event Acknowledge

event_acknowledge
DestructiveIdempotent

Acknowledge Zabbix events to show operations staff are aware of and working on problems; optionally add a message or close resolved alerts.

Instructions

Acknowledge events in Zabbix.

Mark events (problems/alerts) as acknowledged to show that operations staff are aware of and working on the issue. Acknowledged events can also be closed if resolved.

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": {
      "eventids": "<eventids>"
    },
    "name": "event_acknowledge"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNoBitmask: 1=close problem, 2=acknowledge, 4=add message, 8=change severity, 16=unacknowledge, 32=suppress, 64=unsuppress.
messageNoMessage to add to the event. The 'add message' flag (4) is added to 'action' automatically when this is set - Zabbix otherwise accepts the call and stores an empty message, losing the text silently.
eventidsYesEvent IDs to acknowledge.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.6.0
    • changedInput schema / properties / action / default
      Previous value: -1New value: +2
    • changedInput schema / properties / action / description
      Previous value: -"Action: 1=ack, 2=close, 4=add message, etc."New value: +"Bitmask: 1=close problem, 2=acknowledge, 4=add message, 8=change severity, 16=unacknowledge, 32=suppress, 64=unsuppress."
    • addedInput schema / properties / eventids / minItems
      Added value: +1
    • changedInput schema / properties / message / description
      Previous value: -"Optional message to add when acknowledging (e.g., \"Working on this\", \"Will restart service\")."New value: +"Message to add to the event. The 'add message' flag (4) is added to\n     'action' automatically when this is set - Zabbix otherwise accepts\n     the call and stores an empty message, losing the text silently."
  2. 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=true and destructiveHint=true, so the safety profile is carried structurally. The description adds real context about what acknowledgement means operationally and hints that closing is possible, but it never warns that the action bitmask can close problems or change severity — the destructive edges of this tool go unmentioned.

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?

Three short sentences, front-loaded with the action and followed by the operational rationale. No filler, though the last sentence about closing drifts slightly from the tool's core purpose.

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?

An output schema exists so return values need no explanation, and the three parameters are fully documented in schema. What remains thin is bulk semantics — whether multiple eventids are all-or-nothing — but overall an agent has enough to invoke it correctly.

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 itself documents the action bitmask and the auto-adding of flag 4 for messages in detail. The description adds nothing about eventids (single vs. bulk), partial failures, or the action parameter, so the baseline 3 is appropriate.

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+resource ('Acknowledge events in Zabbix') and clarifies that the targets are problems/alerts, which separates it from the read-side sibling event_get. It does not explicitly name the sibling, so it stops short of a 5.

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?

It gives the operational intent (show staff are aware and working the issue) and notes that events can also be closed if resolved, which implies when to reach for it. There is no explicit guidance on when not to use it, no mention of the alternate siblings (event_get, problem_get), and no stated prerequisites.

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