Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

Event Get

event_get
Read-onlyIdempotent

Retrieve Zabbix events to track trigger state changes, problem and recovery alerts, with filters for time, hosts, triggers, acknowledgement, and suppression.

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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "event_get"
  }
}

Input 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. An empty list matches none.
eventidsNoList of event IDs to get. Omit to return all events; an empty list matches none.
groupidsNoList of host group IDs to get events from. An empty list matches none.
objectidsNoList of trigger IDs to get events from. An empty list matches none.
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

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.7.1
    • changedInput schema / properties / eventids / description
      Previous value: -"List of event IDs to get. If empty, returns all events."New value: +"List of event IDs to get. Omit to return all events; an empty list matches none."
    • changedInput schema / properties / groupids / description
      Previous value: -"List of host group IDs to get events from."New value: +"List of host group IDs to get events from. An empty list matches none."
    • changedInput schema / properties / hostids / description
      Previous value: -"List of host IDs to get events from."New value: +"List of host IDs to get events from. An empty list matches none."
    • changedInput schema / properties / objectids / description
      Previous value: -"List of trigger IDs to get events from."New value: +"List of trigger IDs to get events from. An empty list matches none."
  2. 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"
  3. 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, idempotentHint and destructiveHint=false, so the safety profile is covered structurally. The description adds useful semantic context (event lifecycle, ack meaning) but says nothing about result volume, default limit of 100, or that paging requires a deterministic sort — the one behavior an agent most needs to know before calling.

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 no redundant restatement of the tool name. The trailing explanatory sentences are slightly verbose but earn their place by defining what an event is.

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?

With 17 optional parameters and rich per-parameter documentation plus an output schema, the description only needs to frame the resource, which it does. Minor gaps remain around how filters combine and default truncation at 100 results, but nothing essential for correct invocation is missing.

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 nearly every parameter is already documented, including default limit, offset paging via has_more/total, and empty-list-matches-none semantics. The description adds no parameter meaning beyond that, which is the expected baseline when the schema does the work.

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 definition opens with a clear specific verb+resource ("Get events from Zabbix") and explains the domain: state-change events from trigger transitions plus recovery events. It implicitly separates itself from problem_get (current state) and event_acknowledge (mutating acknowledgement), though it never names those siblings explicitly.

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?

Usage is only implied through domain explanation; the description never states when to use this versus problem_get or event_acknowledge, nor any prerequisites or filter-combination rules. The mention that events "can be acknowledged" hints at a related tool without routing the agent to it.

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