Skip to main content
Glama
mhajder

Zabbix MCP Server

by mhajder
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

proxy_get

Read-onlyIdempotent

Get Zabbix proxies acting as data collection points for remote network monitoring, enabling local data collection and reporting to the server.

Instructions

Get proxies from Zabbix.

Proxies act as data collection points for Zabbix, allowing monitoring of remote networks without direct connectivity. Proxies collect data locally and report to the Zabbix server.

Input Schema

TableJSON 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.
outputNoextend
searchNoDictionary with search criteria like {'name': 'proxy1'}. Zabbix 7.0 renamed the proxy 'host' field to 'name' and rejects the old one.
proxyidsNoList of proxy IDs to get. If empty, returns all proxies.
sortfieldNoField to sort by. A deterministic sort is required for paging to be consistent.proxyid
sortorderNoSort direction - 'ASC' or 'DESC'.ASC
count_outputNoIf true, returns only the count of matched objects as an integer.
filter_paramsNoAdditional filter parameters for advanced filtering.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed6 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."
    • changedInput schema / properties / search / description
      Previous value: -"Dictionary with search criteria like {'host': 'proxy1'} for name matching."New value: +"Dictionary with search criteria like {'name': 'proxy1'}. Zabbix 7.0\n    renamed the proxy 'host' field to 'name' and rejects the old one."
    • removedInput schema / properties / sortfield / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • changedInput schema / properties / sortfield / default
      Previous value: -nullNew value: +"proxyid"
    • 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"
  2. First observedv0.5.3

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already cover readOnlyHint, idempotentHint, and destructiveHint, so the bar is lower. However, the description adds no behavior context beyond the annotations, such as return format or side effects. It is neutral and does not contradict the annotations.

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 description is two sentences. The first sentence is the core purpose, but the second sentence explains the concept of proxies, which is background information not essential for usage. While not verbose, the extra sentence is not directly tied to tool usage and could be trimmed for greater front-loading.

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?

An output schema is present, so the description need not explain return values. The description, combined with the schema, is sufficient for the agent to understand the tool's role. The only missing element is explicit usage scenarios, which are already captured by the lower usage score.

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 89%, well above the 80% threshold, so the baseline is 3. The description itself does not elaborate on parameters, but the schema provides adequate explanation for most fields. The description adds no additional parameter semantics.

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 states a specific verb ('Get') and a clear resource ('proxies from Zabbix'). This directly distinguishes it from mutation siblings like proxy_create, proxy_update, and proxy_delete, and aligns with the readOnlyHint annotation.

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 provides no explicit guidance on when to use this tool versus alternatives. It lacks any 'when to use' or 'when not to use' clauses, leaving the agent to infer usage solely from the verb 'Get' and the sibling names.

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/mhajder/zabbix-mcp'

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