Skip to main content
Glama
mhajder

Zabbix MCP Server

by mhajder

event_get

Read-onlyIdempotent

Retrieve monitoring events from Zabbix, including problem and recovery events, with filters for time, hosts, groups, triggers, and acknowledgment status.

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 results to skip (for pagination). Requires sortfield to be set.
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.
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

Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint as true, so the safety profile is clear. The description adds context about event state changes but does not disclose additional behavioral traits beyond what annotations provide. It does not contradict annotations.

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 three sentences, front-loaded with the core purpose, and every sentence adds value. It is concise with no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

While an output schema likely exists (context indicates 'Has output schema: true'), the description does not mention filtering capabilities, pagination (limit/offset), or the variety of parameters. Given the complexity of 17 parameters, the description feels incomplete for guiding parameter usage, though schema covers details.

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 94%, so the schema already documents most parameters. The description does not add parameter-specific meaning beyond the schema. It explains the concept of events but not how to use the many filtering options, so it meets the baseline but does not exceed it.

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 'Get events from Zabbix' and explains what events represent, distinguishing it from sibling tools like event_acknowledge. It uses a specific verb-resource combination and provides context about the nature of events.

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 description explains what the tool does but does not explicitly guide when to use it versus alternatives like problem_get or trigger_get. There is no mention of when-not-to-use or preferred scenarios, leaving the agent to infer from the name alone.

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