Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

Trigger Delete

trigger_delete
Destructive

Permanently remove one or more Zabbix triggers to stop hosts from generating alerts for specific conditions while retaining historical data.

Instructions

Delete triggers from Zabbix.

Permanently removes one or more triggers. Hosts will no longer generate alerts for these conditions. Historical trigger data and associated problems are typically retained.

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": {
      "triggerids": "<triggerids>"
    },
    "name": "trigger_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
triggeridsYesTrigger IDs to delete.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.0
    • addedInput schema / properties / triggerids / minItems
      Added value: +1
  2. First observedv0.5.3

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, and the description adds useful behavioral context: removal is permanent, hosts stop generating alerts for the conditions, and historical trigger data/problems are typically retained. It does not cover permissions or error behavior for repeated deletion, but it meaningfully supplements 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three short sentences, front-loaded with the core action and followed by consequences. Every sentence adds relevant information with no wasted text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained. Given the destructive annotations and the description's explanation of permanence, alert impact, and data retention, the definition is complete for a one-parameter delete tool.

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?

There is only one parameter, triggerids, and the schema description coverage is 100%, so the schema already documents it fully. The description does not add syntax or format details beyond what the schema provides, making the baseline 3 appropriate.

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 states a specific verb and resource: delete triggers from Zabbix. It also clarifies that this permanently removes one or more triggers, distinguishing it from trigger_get, trigger_create, and trigger_update.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the destructive delete action, but the description does not explicitly say when to use this tool versus alternatives such as updating or disabling a trigger. No prerequisites or exclusions are stated.

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