Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

Hostgroup Delete

hostgroup_delete
Destructive

Permanently removes one or more Zabbix host groups by group ID; member hosts remain in Zabbix but are no longer associated with the deleted groups.

Instructions

Delete host groups from Zabbix.

Permanently removes one or more host groups. Hosts in deleted groups will no longer be members of that group (though the hosts themselves remain unless explicitly deleted).

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": {
      "groupids": "<groupids>"
    },
    "name": "hostgroup_delete"
  }
}

Input Schema

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

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, so the description earns credit for going further: it states deletion is permanent and explains the cascade — group membership is severed while host entities persist unless separately deleted. It stops short of covering downstream objects tied to the group (items, triggers) or permission requirements.

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?

Three short sentences, front-loaded with the action, and the cascade note is placed where it matters. The first two sentences overlap slightly ('Delete host groups' / 'Permanently removes one or more host groups'), a minor redundancy.

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?

With an output schema present and 100% schema coverage, the description needn't detail return values, and it covers the destructive semantics well. The remaining gap is the fate of items, triggers, and templates associated with the deleted group, which an agent doing impact assessment would want.

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 coverage is 100% and the single groupids parameter is documented in-schema as 'Group IDs to delete.' The description's 'one or more host groups' only mildly reinforces that the parameter accepts a list, so baseline 3 applies.

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 leads with a specific verb and resource ('Delete host groups from Zabbix') and restates the scope as one or more groups. It's unambiguous what the tool does, but it doesn't differentiate itself from siblings like hostgroup_update or hostgroup_create beyond the verb.

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 delete verb but there is no explicit when-to-use / when-not-to-use guidance, no mention of prerequisites like permissions, and no pointer to hostgroup_update as the non-destructive alternative. The note that hosts survive deletion gives partial context, but routing guidance is absent.

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