Skip to main content
Glama
mhajder

Zabbix MCP Server

by mhajder

trigger_get

Read-onlyIdempotent

Retrieve triggers from Zabbix based on filters like host, group, severity, or description. Get details on problem conditions and their current state.

Instructions

Get triggers from Zabbix.

Triggers are rules that define when a problem occurs based on item values. They evaluate expressions against collected metrics and transition between problem and normal states.

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
searchNoDictionary with search criteria like {'description': 'CPU'}.
hostidsNoList of host IDs to get triggers from.
groupidsNoList of group IDs to get triggers from hosts in those groups.
only_trueNoOnly return triggers in problem state.
sortfieldNoField to sort by.
sortorderNoSort direction - 'ASC' or 'DESC'.ASC
triggeridsNoList of trigger IDs to get. If empty, returns all triggers.
templateidsNoList of template IDs to get triggers from those templates.
count_outputNoIf true, returns only the count of matched objects as an integer.
min_severityNoMinimum severity (0-5).
select_hostsNoIf true, include the hosts each trigger belongs to in the response (selectHosts=extend).
filter_paramsNoAdditional filter parameters for advanced filtering.
description_containsNoShortcut to search for triggers by description (name) (constructs search={'description': description_contains}).

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=true, idempotentHint=true, destructiveHint=false. Description adds context about triggers' role (problem states) but no additional behavioral traits beyond annotations. No contradiction.

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?

Two sentences, front-loaded with the action, no wasted words. Efficiently conveys purpose and concept.

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 16 parameters, high schema coverage, and an output schema, the description explains the trigger concept well. Lacks mention of pagination or typical use cases, but still fairly complete.

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%, and the description does not add any parameter-specific meaning beyond the schema. Baseline 3 applies.

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 the verb 'Get' and the resource 'triggers from Zabbix', and explains what triggers are, distinguishing it from sibling tools like host_get or event_get.

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 on when to use this tool vs alternatives like problem_get or event_get. The description only explains triggers but does not provide usage context or exclusions.

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