Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

Trigger Get

trigger_get
Read-onlyIdempotent

Retrieve Zabbix triggers to identify problem conditions, filter by host, group, template, severity, or description, and page results for monitoring analysis.

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.

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": "trigger_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
searchNoDictionary with search criteria like {'description': 'CPU'}.
hostidsNoList of host IDs to get triggers from. An empty list matches none.
groupidsNoList of group IDs to get triggers from hosts in those groups. An empty list matches none.
only_trueNoOnly return triggers in problem state.
sortfieldNoField to sort by. A deterministic sort is required for paging to be consistent.triggerid
sortorderNoSort direction - 'ASC' or 'DESC'.ASC
triggeridsNoList of trigger IDs to get. Omit to return all triggers; an empty list matches none.
templateidsNoList of template IDs to get triggers from those templates. An empty list matches none.
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

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.7.1
    • changedInput schema / properties / groupids / description
      Previous value: -"List of group IDs to get triggers from hosts in those groups."New value: +"List of group IDs to get triggers from hosts in those groups. An empty list matches none."
    • changedInput schema / properties / hostids / description
      Previous value: -"List of host IDs to get triggers from."New value: +"List of host IDs to get triggers from. An empty list matches none."
    • changedInput schema / properties / templateids / description
      Previous value: -"List of template IDs to get triggers from those templates."New value: +"List of template IDs to get triggers from those templates. An empty list matches none."
    • changedInput schema / properties / triggerids / description
      Previous value: -"List of trigger IDs to get. If empty, returns all triggers."New value: +"List of trigger IDs to get. Omit to return all triggers; 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: +"triggerid"
    • 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

C2.9/5.0
Behavior2/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. The description adds only domain background (triggers evaluate expressions and transition between problem/normal states), not operational behavior such as pagination semantics, volume expectations, or how counts are returned.

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?

Two short sentences, front-loaded with the action. The second sentence is domain education rather than routing information, but it does help an agent interpret results, so it mostly earns its place.

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?

With an output schema and rich annotations, the description needn't explain return values, and the schema documents 16 parameters well. What is missing is the selection guidance an agent needs to choose this tool over its many read-oriented siblings.

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 explains limit, offset, filters, min_severity, count_output and the rest. The description contributes no additional parameter meaning beyond that, so the baseline 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?

States a specific verb and resource ("Get triggers from Zabbix") and adds a definition of what a trigger is. It is clearly a read/list operation, distinguishable from trigger_create/update/delete siblings by the verb, though it never contrasts with sibling read tools like problem_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?

There is no explicit when-to-use guidance: nothing says when to prefer trigger_get over problem_get or event_get, nor when to use only_true or filters. Usage is only implied by the tool name and the parameter list.

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