Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

Hostgroup Create

hostgroup_create

Create a host group in Zabbix to organize hosts and apply permissions, templates, and maintenance windows to multiple hosts at once.

Instructions

Create a new host group in Zabbix.

Host groups serve as containers for organizing hosts. They're essential for applying permissions, templates, and maintenance windows to multiple hosts at once.

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

Input Schema

NameRequiredDescriptionDefault
nameYesName of the host group.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.3

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the agent knows this is a non-destructive, non-idempotent write. The description adds useful domain context about why host groups matter (permissions, templates, maintenance windows) but does not say what happens if the name already exists, which is the most likely failure mode for a non-idempotent create.

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 core action is front-loaded in the first sentence, and the follow-up paragraph is brief and informative rather than repetitive. It could be tightened, but nothing is wasted verbatim on restating the name or title.

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

Completeness3/5

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

An output schema exists, so return values need no explanation, and annotations cover the safety profile. However, for a non-idempotent create the description should mention duplicate-name behavior or scope (per-host vs global), which it omits; the tool is simple, but that remaining gap is a real one an agent would hit.

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?

There is a single parameter with 100% schema description coverage, which sets the baseline at 3. The description adds no meaning beyond the schema — nothing about name uniqueness, allowed characters, or length — so it neither compensates nor subtracts.

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 first sentence names a specific verb and resource: "Create a new host group in Zabbix." That is unambiguous and the create/get/update/delete siblings make the intent obvious. It stops short of explicitly contrasting itself with hostgroup_update or hostgroup_get, so it is clear but not sibling-differentiating.

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?

The description never says when to use this versus hostgroup_update or host_create, and gives no prerequisites such as required auth or whether the host group must already exist somewhere. The second paragraph explains what host groups are for conceptually, which is background rather than invocation guidance.

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