Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

Maintenance Delete

maintenance_delete
Destructive

Delete Zabbix maintenance periods to cancel active maintenance windows immediately and resume alert generation; past suppression remains intact.

Instructions

Delete maintenance periods from Zabbix.

Cancels maintenance windows immediately, resuming alert generation. If the maintenance period has already passed, historical event suppression is 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": {
      "maintenanceids": "<maintenanceids>"
    },
    "name": "maintenance_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
maintenanceidsYesMaintenance 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 / maintenanceids / minItems
      Added value: +1
  2. First observedv0.5.3

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already set destructiveHint=true and idempotentHint=false, so the bar is lower. The description still adds genuine behavioral context beyond those flags: alert generation resumes immediately on cancel, and already-passed periods keep their historical suppression, which affects how an agent should reason about the consequences of deletion.

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?

Three short sentences with the purpose front-loaded followed by two clauses that each carry distinct behavioral information: immediate alert resumption and retained historical suppression.

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?

For a single-parameter destructive mutation with annotations and an output schema, the description covers the essential side effects a caller must know. The only remaining gap is error behavior for invalid or not-found IDs, which is a minor omission.

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% and the single required parameter (maintenanceids array) is documented there, so baseline is 3. The description adds nothing about batching, how nonexistent or already-deleted IDs are handled, or whether partial success is possible.

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 ('Delete maintenance periods from Zabbix'), which an agent can immediately distinguish from the maintenance_get, maintenance_create, and maintenance_update siblings. It doesn't explicitly name those alternatives, so it stops 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 Guidelines3/5

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

The description makes clear what deleting accomplishes (cancels windows, resumes alert generation), which implies when to reach for it, but it never states when-not to use it or points to maintenance_update as the way to modify rather than remove a window. Usage is implied rather than guided.

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