Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

Hostgroup Update

hostgroup_update

Update an existing Zabbix host group by modifying its name or other properties. Specify only the fields you want to change.

Instructions

Update an existing host group in Zabbix.

Modifies properties of an existing host group. You can change the group's name. Only specify the fields you want to change.

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

Input Schema

NameRequiredDescriptionDefault
nameNoNew group name.
groupidYesID of the group to update.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.3

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the safety profile is covered. The description usefully narrows the mutation scope to renaming only, but it does not address behavior the annotations flag, such as non-idempotency or what happens when the groupid does not exist.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The first two sentences restate the same fact ('Update an existing host group' / 'Modifies properties of an existing host group'), which is wasted space. The genuinely useful line about specifying only changed fields is buried last rather than front-loaded.

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 not be explained, and the annotations cover the safety profile. For a mutation tool, however, the description says nothing about error conditions or whether group names must be unique — a gap an agent would likely hit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real semantic meaning by stating that fields are optional and only changed fields should be sent — critical since groupid is the sole required parameter. It does not add format or constraint detail beyond that.

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?

States a specific verb and resource ('Update an existing host group in Zabbix') and clarifies via the schema that only the group name is mutable. The sibling set (hostgroup_create/delete/get) makes the distinction by name straightforward, though the description itself does not call out those siblings.

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?

'Only specify the fields you want to change' gives concrete guidance on how to invoke it as a partial update, which is the main decision an agent faces here. It stops short of explicit when-to-use/when-not or naming alternatives like hostgroup_create.

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