Skip to main content
Glama
mhajder

Zabbix MCP Server

by mhajder

event_get

Read-onlyIdempotent

Retrieve Zabbix events to identify state changes, including trigger problems and recoveries. Filter by hosts, groups, time range, or acknowledgement status to monitor alerts and support incident response.

Instructions

Get events from Zabbix.

Events represent state changes in the system - when triggers transition from normal to problem and back, or recovery events. Each event has a timestamp, trigger, and can be acknowledged to show operators have seen the alert.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return. Default is 100.
offsetNoNumber of matching records to skip. Use with 'limit' to page through results; check 'has_more' and 'total' in the response.
outputNoextend
hostidsNoList of host IDs to get events from.
eventidsNoList of event IDs to get. If empty, returns all events.
groupidsNoList of host group IDs to get events from.
objectidsNoList of trigger IDs to get events from.
sortfieldNoField to sort by. A deterministic sort is required for paging to be consistent.eventid
sortorderNoSort direction - 'ASC' or 'DESC'.ASC
time_fromNoUnix timestamp to filter events from this time onwards.
time_tillNoUnix timestamp to filter events up to this time.
suppressedNoIf false, return only unsuppressed events. If true, return only suppressed events.
select_tagsNoIf true, include the tags for each event in the response (selectTags=extend).
acknowledgedNoIf false, return only unacknowledged events. If true, return only acknowledged events.
count_outputNoIf true, returns only the count of matched objects as an integer.
select_hostsNoIf true, include the hosts each event belongs to in the response (selectHosts=extend).
select_related_objectNoIf true, include the related object (e.g., trigger) in the response (selectRelatedObject=extend).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

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

  1. Changed5 schema fields changedv0.6.0
    • changedInput schema / properties / offset / description
      Previous value: -"Number of results to skip (for pagination). Requires sortfield to be set."New value: +"Number of matching records to skip. Use with 'limit' to page through results; check 'has_more' and 'total' in the response."
    • removedInput schema / properties / sortfield / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • changedInput schema / properties / sortfield / default
      Previous value: -nullNew value: +"eventid"
    • changedInput schema / properties / sortfield / description
      Previous value: -"Field to sort by."New value: +"Field to sort by. A deterministic sort is required for paging to be consistent."
    • addedInput schema / properties / sortfield / type
      Added value: +"string"
  2. 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 cover the read-only, idempotent, and non-destructive nature of the tool, so the description does not need to repeat that. The description adds domain context (events are state changes, can be acknowledged) but does not disclose additional behavioral traits like pagination behavior or default sorting beyond what the schema already documents.

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 concise, starting with the core action and then adding a compact explanation of events. Each sentence adds relevant context without excessive verbosity, and the structure is logical (action first, then background).

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 high parameter schema coverage and the presence of an output schema, the description is sufficient to understand the tool's domain and purpose. It explains what an event is, which is essential for an agent to decide when to use it. The only minor gap is the lack of explicit mention of pagination, but the offset parameter description already covers that.

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 high (94%), so the parameters are well-documented in the input schema. The description provides general context about events that helps interpret parameters like objectids (trigger IDs) and time filters, but it does not add specific parameter-level semantics beyond what the schema already offers.

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 clearly states the core action 'Get events from Zabbix' and elaborates on what events represent (state changes, trigger transitions, acknowledgments). It is specific about the resource but does not explicitly differentiate from sibling tools like problem_get or history_get, though the name and context make the purpose clear.

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?

No guidance is provided on when to use this tool versus alternatives. The description explains the concept of events but does not mention scenarios where event_get is preferable to problem_get, history_get, or trend_get. There is no discussion of trade-offs or selection criteria.

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

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