Skip to main content
Glama
initMAX

Zabbix MCP Server

connector_get

Read-only

Retrieve Zabbix event connectors to review endpoints, data formats, authentication, and event filtering for SIEM integrations, custom pipelines, and third-party alerting.

Instructions

Retrieve event connectors. Connectors stream Zabbix events to external systems in real time, enabling SIEM integration, custom event pipelines, and third-party alerting. Each connector defines a URL endpoint, data format, authentication, and filtering rules for which events to forward.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return.
filterNoReturn 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: attempt_interval (7.0+), authtype, connectorid, data_type, http_proxy, item_value_type (7.0+), max_attempts, max_records, max_senders, name, password, protocol, ssl_cert_file, ssl_key_file, ssl_key_password, status, tags_evaltype, timeout, token, url, username, verify_host, verify_peer. Text properties cannot be filtered; use 'search' for them.
outputNoProperties of the connector 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: connectorid, name, status. Properties: attempt_interval (7.0+), authtype, connectorid, data_type, description, http_proxy, item_value_type (7.0+), max_attempts, max_records, max_senders, name, password, protocol, ssl_cert_file, ssl_key_file, ssl_key_password, status, tags_evaltype, timeout, token, url, username, verify_host, verify_peer.
searchNoReturn results whose string properties contain the given pattern (case-insensitive; '*' is a wildcard when searchWildcardsEnabled is true). Example: {"name": "web"}. Keys: attempt_interval (7.0+), description, http_proxy, name, password, ssl_cert_file, ssl_key_file, ssl_key_password, timeout, token, url, username.
serverNoTarget Zabbix server. Available: default. Defaults to 'default' if omitted.
raw_jsonNoStrips 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.
sortfieldNoSort by one or more of: connectorid, name, data_type, status (comma-separated for several; pair with 'sortorder'). No other property is sortable.
sortorderNoSort order: 'ASC' (ascending) or 'DESC' (descending).
countOutputNoReturn the count of matching results instead of the actual data.
searchByAnyNoIf true, return results matching ANY search field (OR). Default is ALL fields (AND).
connectoridsNoReturn only connectors with the given IDs.
extra_paramsNoOther native connector.get parameters, merged into the request as-is. Sub-object selects (value 'extend', 'count' or a list of property names): selectTags. 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.
searchWildcardsEnabledNoIf true, enable * and ? wildcards in search patterns.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.41.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered without description help. The description adds no behavioral context beyond that — nothing about pagination, default output fields, result volume, or the security-disclaimer wrapping that the raw_json parameter implies — so it does not clear even the lowered bar for annotated tools.

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?

Three sentences, front-loaded with the actionable verb+resource. The two follow-up sentences are background rather than invocation help, but they are short and orient a reader unfamiliar with Zabbix connectors.

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?

For a read-only retrieval tool with an output schema, full annotation coverage, and 100% schema documentation, the definition supplies enough to call it correctly. The only material gap is the absence of usage/routing guidance, which the rich schema largely compensates for.

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 every one of the 13 optional parameters carries its own detailed documentation (filter keys, output modes, sort fields, raw_json policy caveats, extra_params fallback). The description says nothing about any parameter, 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?

The first sentence states a specific verb+resource ("Retrieve event connectors") and the remainder explains what a connector is in Zabbix terms, so an agent immediately knows the object being fetched. There is no sibling connector_* tool to distinguish from, so the lack of explicit differentiation costs little, but the description never states scope (all connectors vs. filtered) beyond what the schema implies.

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 explains the domain (SIEM integration, alerting) but gives no guidance on when to call this tool, no mention of prerequisites, and no pointer to alternatives such as zabbix_raw_api_call for unsupported parameters. Usage must be inferred entirely from the name and schema.

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