Zabbix MCP Server

Overview Schema Source Related Servers Discussions Admin

proxygroup_get

Read-only

Retrieve Zabbix proxy groups to manage high availability and load balancing for data collection, filter by name or state, and include member proxies.

Instructions

Retrieve proxy groups. Proxy groups provide high availability and load balancing for data collection by grouping multiple proxies. Hosts assigned to a proxy group are automatically distributed among the group's proxies, and failover occurs if a proxy becomes unavailable. Use selectProxies to include the group's member proxies.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of results to return.
`filter`	No	Return only results whose properties exactly match the given values (a single value or a list of values per key). Example: {"status": 0} or {"status": [0, 1]}. Keys: failover_delay, min_online, name, proxy_groupid, state. Text properties cannot be filtered; use 'search' for them.
`output`	No	Properties of the proxygroup object to return. Pass 'extend' for all, 'count' for the number of matches only, or a comma-separated list of property names. Default when omitted: proxy_groupid, name, state. Properties: description, failover_delay, min_online, name, proxy_groupid, state.
`search`	No	Return results whose string properties contain the given pattern (case-insensitive; '*' is a wildcard when searchWildcardsEnabled is true). Example: {"name": "web"}. Keys: description, failover_delay, min_online, name.
`server`	No	Target Zabbix server. Available: default. Defaults to 'default' if omitted.
`raw_json`	No	Strips the security disclaimer preamble from the response so it is pure JSON. Default: false. Requires the bearer token to have 'allow_raw_json' explicitly enabled by an operator in the admin portal - tokens without that policy receive a PolicyError instead. WARNING: setting true bypasses the prompt-injection mitigation marker that wraps untrusted Zabbix data (host names, item descriptions, problem text). LLM clients (Claude, GPT, Cursor, ...) should leave this false; only programmatic non-LLM consumers (Python scripts, n8n workflows that json.loads the result) should set true.
`sortfield`	No	Sort by one or more of: proxy_groupid, name (comma-separated for several; pair with 'sortorder'). No other property is sortable.
`sortorder`	No	Sort order: 'ASC' (ascending) or 'DESC' (descending).
`countOutput`	No	Return the count of matching results instead of the actual data.
`searchByAny`	No	If true, return results matching ANY search field (OR). Default is ALL fields (AND).
`extra_params`	No	Other native proxygroup.get parameters, merged into the request as-is. Parameters: proxy_groupids, proxyids. Sub-object selects (value 'extend', 'count' or a list of property names): selectProxies. Any other key is refused here, because Zabbix would silently ignore it. For a parameter you are sure exists on your release but is not listed, use zabbix_raw_api_call.
`proxygroupids`	No	Return only proxy groups with the given IDs.
`searchWildcardsEnabled`	No	If true, enable * and ? wildcards in search patterns.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.41.0Oct 20, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the agent knows this is a safe read. The description adds useful domain semantics (host distribution and failover across group members), but says nothing about pagination, result size, or how behavior changes when the group is empty/unavailable. With annotations covering the safety profile, this is a modest addition.

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 one sentence, followed by compact supporting context. The two middle sentences on failover and load balancing are somewhat tangential to the act of retrieving groups, but they are brief and aid comprehension rather than padding.

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, return values need no explanation, and annotations handle the read-only safety profile. The description supplies the domain framing needed to interpret results, though it could note whether the list is paginated or bounded. Nothing an agent needs to call it is missing.

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%, so every one of the 13 parameters is already documented in the schema. The description adds only a passing mention of selectProxies, which the schema also covers under extra_params. Baseline 3 is appropriate when the schema does the heavy lifting.

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 leading sentence 'Retrieve proxy groups' gives a specific verb and resource, and the following sentences explain what a proxy group is, which helps disambiguate it from the sibling proxy_get. However, it never explicitly contrasts itself with proxy_get, so an agent must infer the distinction from context rather than the text itself.

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 rather than stated: this is a read operation for proxy groups, and the closing note 'Use selectProxies to include the group's member proxies' is parameter guidance, not when-to-use guidance. It names no alternatives and gives no conditions for choosing this over proxy_get or the other *_get siblings.

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

Deploy Server