Skip to main content
Glama
mhajder

Zabbix MCP Server

by mhajder

trigger_get

Read-onlyIdempotent

Retrieve Zabbix triggers to identify monitoring rules that signal problems, enabling proactive issue detection and infrastructure health checks.

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 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.
groupidsNoList of group IDs to get triggers from hosts in those groups.
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. 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

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 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"
  2. First observedv0.5.3

TDQS

C2.9/5.0
Behavior2/5

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

The annotations (readOnlyHint=true, idempotentHint=true, destructiveHint=false) already cover the safety profile, but the description itself adds no behavioral disclosure beyond the domain statement that triggers 'transition between problem and normal states.' It does not mention pagination, default result size, or that by default no filters are applied.

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?

The description is short and front-loaded with the action verb, and the additional trigger definition is a compact, relevant context sentence. No unnecessary words or repetition of schema fields.

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?

Given the rich schema and output schema, most invocation details are available without the description. However, the description lacks usage guidance—particularly that this tool returns trigger configuration/status and how it relates to problem_get—leaving a clear completeness gap for an agent choosing among 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 input schema already documents nearly all parameters. The description adds no parameter-level semantics; its trigger explanation provides domain context, but with such high schema coverage the description need not compensate, earning the baseline score.

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 opening sentence 'Get triggers from Zabbix' names a specific verb and resource, and the following context explains what triggers are. It is clear and unambiguous, though it does not explicitly distinguish trigger_get from siblings like problem_get or trigger_delete beyond the verb itself.

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 guidance about when to use this tool instead of alternatives. It does not mention that problem_get is preferable for current problem states, nor does it state the default 'returns all triggers' behavior. An agent must infer usage from the name and schema.

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

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