Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

Template Delete

template_delete
Destructive

Permanently delete Zabbix templates by ID. Hosts lose associated items, triggers, and graphs upon template removal, but remain unchanged.

Instructions

Delete templates from Zabbix.

Permanently removes one or more templates. Hosts that have the deleted templates applied will lose those template's items, triggers, and graphs. The hosts themselves remain unchanged.

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": {
      "templateids": "<templateids>"
    },
    "name": "template_delete"
  }
}

Input Schema

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

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false. The description adds substantial behavioral context beyond those flags: deletion is permanent, applied hosts lose the template's items, triggers, and graphs, but the hosts themselves remain. This is exactly the kind of impact disclosure an agent needs for a destructive operation.

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 with the core action front-loaded. Every sentence adds value, especially the cascade impact note, and there is no redundant boilerplate.

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?

For a destructive template-deletion tool with complete input schema coverage, annotations, and an output schema, the description supplies the critical behavioral detail an agent would otherwise lack: permanence and downstream effects on hosts. Nothing essential to correct invocation is missing.

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 parameter 'templateids' is already documented as an array of template IDs. The description's phrase 'one or more templates' is consistent with the schema but does not add meaningful syntax or usage detail beyond it. Baseline 3 is appropriate when the schema carries the parameter documentation.

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 templates from Zabbix. It is clearly distinguishable from sibling tools such as template_get, template_create, and template_update. The additional sentence about permanent removal reinforces rather than obscures the purpose.

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

Usage Guidelines4/5

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

The description makes the use case clear: permanently removing one or more templates. It does not explicitly name alternatives like template_update for non-destructive changes, but the deletion context is unambiguous. The warning about affected hosts gives useful context for when caution is needed.

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