Skip to main content
Glama
mhajder

Zabbix MCP Server

by mhajder
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

event_acknowledge

DestructiveIdempotent

Acknowledge Zabbix events to mark problems as handled, with options to close resolved issues and add messages.

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.

Input Schema

TableJSON 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

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  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

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description discloses that events can be closed if resolved, aligning with the destructiveHint annotation. It also provides context about the purpose (awareness/working on issue) that goes beyond the basic annotations, but does not list potential side effects or error conditions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise, consisting of two sentences that front-load the main action and provide relevant details. It is well-structured and free of unnecessary fluff.

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 description is complete for understanding the tool's purpose and primary behavior. Since an output schema exists, it does not need to explain return values. It covers the key action and the optional closing behavior, though it omits explicit error handling or prerequisites.

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?

The input schema already describes all parameters (action, message, eventids) with 100% coverage. The tool description adds no additional parameter semantics beyond what the schema provides, so the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: to acknowledge events in Zabbix, with a specific action (acknowledge) and resource (events). It also mentions the ability to close resolved events, providing full intent.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains the situational context (showing staff awareness and working on issues) and the effect (closing if resolved), which implies when to use it. However, it does not explicitly contrast with related tools like event_get or problem_get, leaving some inference needed.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mhajder/zabbix-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server