Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

Trigger Create

trigger_create

Create a Zabbix trigger with a custom expression to define when problems are detected and items transition from normal to problem state.

Instructions

Create a new trigger in Zabbix.

Triggers define the conditions under which problems are detected. They use expressions to evaluate item values and determine when to transition from normal to problem state.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "description": "<description>",
      "expression": "<expression>"
    },
    "name": "trigger_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNo0=enabled, 1=disabled.
commentsNoOptional comment/notes about the trigger explaining its purpose and context.
priorityNoSeverity 0-5.
expressionYesTrigger expression.
descriptionYesTrigger description/name.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 already declare that this is a non-read-only, non-idempotent, non-destructive mutation. The description does not add meaningful behavioral detail such as permission requirements, duplicate-handling behavior, validation rules, or side effects, though it does stay consistent with the annotations.

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 purpose stated in the first sentence and supporting domain context in the second. It is appropriately sized, though the second sentence is useful background rather than strictly necessary invocation guidance.

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 full schema coverage, annotations, and an output schema, the description does not need to explain parameters or return values. However, for a create/mutation tool it still lacks context around permissions, uniqueness, or what happens when a duplicate trigger is created, leaving some behavioral gaps.

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 the schema already documents every parameter, including status, priority, expression, and description. The description adds no parameter-specific meaning beyond what the schema provides, making the baseline score of 3 appropriate.

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 specific verb and resource: "Create a new trigger in Zabbix." It adds a concise explanation of what triggers are, but does not explicitly distinguish this tool from nearby siblings such as trigger_update or trigger_get, so it falls just short of a 5.

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 implies that this tool is for new triggers rather than updates, but it gives no explicit guidance on when to use it versus trigger_update or trigger_get. It also does not mention prerequisites, exclusions, or common call conditions.

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