Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

Host Delete

host_delete
Destructive

Permanently removes one or more Zabbix hosts and all associated history and alerts; use cautiously because deletion is destructive.

Instructions

Delete hosts from Zabbix.

Permanently removes one or more hosts from Zabbix. This will delete all associated data including history and alerts. Use with caution as this is a destructive operation.

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": {
      "hostids": "<hostids>"
    },
    "name": "host_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostidsYesList of host 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 / hostids / 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?

The annotations already declare destructiveHint=true, but the description adds important scope: deletion is permanent and removes all associated data including history and alerts. This is exactly the kind of behavioral consequence an agent needs beyond the annotation flags.

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 short, front-loaded, and structured around the core action, its permanence, and the destructive warning. Every sentence contributes useful information without unnecessary elaboration.

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?

Given the single fully documented parameter, existing annotations, and an output schema, the description provides everything needed for correct invocation. It covers the action, scope of deletion, and the critical destructive consequence.

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?

The schema has 100% description coverage and clearly documents hostids as the list of host IDs to delete. The description adds only that one or more hosts are removed, which aligns with the schema but does not expand on parameter semantics beyond it.

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 uses a specific verb and resource: "Delete hosts from Zabbix" and "Permanently removes one or more hosts." It clearly distinguishes this tool from sibling operations like host_create, host_update, and host_get by stating the destructive host-removal 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?

It clearly establishes the destructive context and warns "Use with caution," which helps an agent decide when this tool is appropriate. However, it does not explicitly name alternatives or conditions where deletion should not be used, such as preferring host_update for changes.

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