Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

Hostgroup Get

hostgroup_get
Read-onlyIdempotent

Retrieve Zabbix host groups with optional filters, sorting, and pagination to organize hosts, apply templates and permissions, and inspect group membership.

Instructions

Get host groups from Zabbix.

Retrieves host groups with optional filtering. Host groups are used to organize and manage hosts collectively, applying templates, permissions, and maintenance windows to multiple hosts at once.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "hostgroup_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return. Default is 100.
offsetNoNumber of matching records to skip. Use with 'limit' to page through results; check 'has_more' and 'total' in the response.
outputNoOutput format.extend
searchNoSearch.
hostidsNoHost IDs. An empty list matches none.
groupidsNoGroup IDs. An empty list matches none.
sortfieldNoField to sort by. A deterministic sort is required for paging to be consistent.groupid
sortorderNoSort direction - 'ASC' or 'DESC'.ASC
count_outputNoIf true, returns only the count of matched objects as an integer.
select_hostsNoIf true, include the hosts in each group in the response (selectHosts=extend).
group_name_containsNoShortcut to search for groups by name (constructs search={'name': group_name_contains}).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.7.1
    • changedInput schema / properties / groupids / description
      Previous value: -"Group IDs."New value: +"Group IDs. An empty list matches none."
    • changedInput schema / properties / hostids / description
      Previous value: -"Host IDs."New value: +"Host IDs. An empty list matches none."
  2. Changed5 schema fields changedv0.6.0
    • changedInput schema / properties / offset / description
      Previous value: -"Number of results to skip (for pagination). Requires sortfield to be set."New value: +"Number of matching records to skip. Use with 'limit' to page through results; check 'has_more' and 'total' in the response."
    • removedInput schema / properties / sortfield / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • changedInput schema / properties / sortfield / default
      Previous value: -nullNew value: +"groupid"
    • changedInput schema / properties / sortfield / description
      Previous value: -"Field to sort by."New value: +"Field to sort by. A deterministic sort is required for paging to be consistent."
    • addedInput schema / properties / sortfield / type
      Added value: +"string"
  3. 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, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds domain context about what host groups represent, but says nothing about result size, paging behavior, or permission scoping beyond the schema.

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?

Two short paragraphs with the action front-loaded in the first sentence. The second paragraph is explanatory domain filler that aids understanding but does not directly help invocation, keeping it just short of a 5.

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, full parameter documentation, and read-only annotations, the description does not need to restate return values or paging mechanics. What remains thin is guidance on when to reach for this tool, which is covered under usage rather than completeness.

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 description coverage is 100% and each parameter (limit, offset, search, group_name_contains, select_hosts, count_output) is documented inline with defaults and semantics. The description only generically mentions 'optional filtering' and adds nothing beyond the schema, 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?

States a specific verb and resource ('Get host groups from Zabbix') and clarifies the object being retrieved, which distinguishes it from host_get or trigger_get by resource. It does not explicitly contrast with siblings like hostgroup_create/update/delete, so it stops short of a 5.

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?

Says retrieval supports 'optional filtering' but gives no guidance on when to use this versus host_get, trigger_get, or the hostgroup mutation siblings, and no prerequisites or exclusions. An agent must infer usage from parameter names alone.

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