Skip to main content
Glama
leroylim

Zabbix MCP Server

by leroylim

zabbix_delete_hostgroups

Delete Zabbix host groups by specifying their group IDs. Removes unwanted groups to keep your monitoring organized.

Instructions

Delete host groups from Zabbix

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupidsYesArray of host group IDs to delete
Behavior1/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only says 'Delete host groups' with no mention of permanence, side effects on associated hosts/templates, permission requirements, or potential failure modes. This is a significant gap 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.

Conciseness4/5

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

The description is a single concise sentence with no redundant words. It is appropriately sized for a simple tool, though it could include more context without being verbose. The structure is clean and front-loaded with the action.

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

Completeness2/5

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

The tool is straightforward but destructive, with no annotations and no output schema. The description fails to explain important context such as consequences, required permissions, or interaction with other resources (e.g., hosts linked to a group). It is minimal and inadequate for an agent to safely invoke the 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?

The input schema provides 100% coverage with a clear description for groupids ('Array of host group IDs to delete'). The tool description adds no additional parameter semantics, but since the schema already covers all parameters, the baseline of 3 applies.

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 clearly states the action 'Delete' and the resource 'host groups' with the target system 'Zabbix'. It is specific and distinguishes from siblings such as zabbix_create_hostgroup, zabbix_update_hostgroup, and zabbix_get_hostgroups.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives, such as when to use update instead of delete, or any prerequisites like checking for dependencies. The description only offers the basic purpose without context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/leroylim/zabbix-mcp-server-nodejs'

If you have feedback or need assistance with the MCP directory API, please join our Discord server