Skip to main content
Glama
leroylim

Zabbix MCP Server

by leroylim

zabbix_get_triggers

Retrieve Zabbix triggers by applying filters for hosts, groups, severity, or problem state, and specify which fields to return.

Instructions

Get triggers from Zabbix with filtering and output options

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoLimit the number of records returned
filterNoReturn only triggers that match the given filter
outputNoObject properties to be returned
searchNoReturn only triggers that match the given wildcard search
hostidsNoReturn only triggers that belong to the given hosts
groupidsNoReturn only triggers that belong to hosts in the given host groups
monitoredNoReturn only enabled triggers that belong to monitored hosts
only_trueNoReturn only triggers that are in problem state
sortfieldNoSort the result by the given properties
sortorderNoSort orderDESC
triggeridsNoReturn only triggers with the given trigger IDs
selectHostsNoReturn hosts that the trigger belongs to
selectItemsNoReturn items that are used in the trigger
templateidsNoReturn only triggers that belong to the given templates
min_severityNoReturn only triggers with severity greater or equal
expandDescriptionNoExpand macros in the trigger description
Behavior2/5

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

No annotations are supplied, so the description carries the full burden of disclosing behavior. It does not mention that this is a read-only operation, any authentication requirements, performance implications of broad queries, or the default output format. The phrase 'with filtering and output options' only echoes schema features without adding behavioral insights.

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 that communicates the core purpose and hints at additional capabilities. It is front-loaded and contains no fluff, making it easy to parse quickly.

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 (16 parameters, no required fields, nested objects, no output schema), the description is far from complete. It does not describe the return value, any pagination behavior, or how the tool relates to other Zabbix operations. The absence of annotations and an output schema makes this a significant gap.

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 100%, so baseline is 3. The description adds no parameter-specific details beyond the schema's own field descriptions. It mentions 'filtering and output options' but does not explain any parameter syntax or semantics beyond what is already in the input schema.

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 'Get triggers from Zabbix' clearly identifies the resource (triggers) and the verb (get), distinguishing it from sibling tools like zabbix_get_problems or zabbix_get_items. The mention of filtering and output options reinforces the purpose without ambiguity.

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 about when to use this tool versus alternatives. The description does not mention any specific use cases, preconditions, or exclusions, leaving the agent without context on when to choose this over related tools like get_problems or get_events.

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