Skip to main content
Glama
leroylim

Zabbix MCP Server

by leroylim

zabbix_get_events

Retrieve Zabbix events by host, severity, time, and tag filters to identify and resolve monitoring problems.

Instructions

Retrieves events from Zabbix with filtering options.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoArray of tag filters.
limitNoMaximum number of events to return.
valueNoEvent values: 0 (OK), 1 (problem).
objectNoEvent object type.
outputNoOutput fields.extend
sourceNoEvent source: 0 (trigger), 1 (discovery), 2 (auto registration), 3 (internal).
hostidsNoArray of host IDs to filter events by.
evaltypeNoEvaluation type: 0 (AND/OR), 2 (OR).
eventidsNoArray of event IDs to retrieve.
groupidsNoArray of host group IDs to filter events by.
objectidsNoArray of object IDs (trigger IDs) to filter events by.
sortfieldNoFields to sort by.
sortorderNoSort order.DESC
time_fromNoStart time for event filtering.
time_tillNoEnd time for event filtering.
selectTagsNoInclude event tags.
severitiesNoArray of severity levels to filter by (0-5).
selectHostsNoInclude host information.
acknowledgedNoFilter by acknowledgment: 0 (unacknowledged), 1 (acknowledged).
selectRelatedObjectNoInclude related object information.
selectSuppressionDataNoInclude suppression data.
Behavior2/5

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

With no annotations, the description must disclose behavioral traits, but it does not mention read-only nature, pagination limits, return format variations (e.g., 'extend' vs 'count'), or any side effects. It only states the core action without behavioral details.

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 a single concise sentence with no unnecessary words. It is front-loaded with the verb and resource, making it efficient and appropriately sized.

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

Completeness2/5

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

Given the tool's complexity (21 parameters) and lack of annotations or output schema, the description is severely under-specified. It provides no high-level context, use cases, or relationships to sibling tools, leaving the agent without adequate guidance.

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 provides 100% coverage of all 21 parameters, each with descriptions and enums. The description adds no additional parameter semantics beyond what the schema already provides, so the baseline of 3 applies.

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 tool retrieves events from Zabbix and mentions filtering options. It uses a specific verb and resource, but does not differentiate it from sibling tools like zabbix_get_problems or zabbix_get_alerts.

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?

The description provides no guidance on when to use this tool versus alternatives. There is no mention of use cases, exclusions, or alternative tools; usage is only implied by the tool name and description.

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/leroylim/zabbix-mcp-server-nodejs'

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