Zabbix MCP Server

Overview Schema Source Related Servers Discussions Admin

correlation_get

Read-only

Retrieve Zabbix event correlation rules to see how related problem events are automatically closed, filtered, searched, sorted, or counted.

Instructions

Retrieve event correlations. Correlations define rules for automatically closing related problem events. For example, a correlation can close all 'service down' problems when a 'service up' event is received.

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: correlationid, name, status. Text properties cannot be filtered; use 'search' for them.
`output`	No	Properties of the correlation 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: correlationid, name, status. Properties: correlationid, description, name, status.
`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, 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: correlationid, name, status (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 correlation.get parameters, merged into the request as-is. Sub-object selects (value 'extend', 'count' or a list of property names): selectFilter, selectOperations. 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.
`correlationids`	No	Return only correlations 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

B3.2/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 safety profile is covered. The description adds conceptual context about what correlations do but says nothing about the call's behavior itself (result volume, defaults, the raw_json security caveat that lives only in the schema). With annotations carrying the safety burden, a 3 is appropriate.

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 short sentences, front-loaded with the action and resource, then a definition and a concrete example. The example earns its place by clarifying the domain concept, though it could be trimmed slightly without loss.

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 exists, so return values need no explanation, and every parameter is fully documented in the schema. For a read-only, all-optional-parameter getter the description covers purpose and domain adequately; the only real gap is usage/routing guidance, which is scored separately.

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% across all 13 parameters, so the schema already documents filtering, output selection, sorting, search semantics and the raw_json policy. The description adds no parameter-level meaning, so the 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 ('Retrieve event correlations') and then explains what a correlation actually is, which helps an agent interpret the returned objects. The resource is unique among the siblings (the closest, ceprule_get, is a different concept), so no explicit sibling differentiation is strictly needed, but none is offered either.

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 never says when to use this tool versus alternatives, nor any prerequisites or context of use. It is purely definitional/educational; an agent gets no routing guidance. Only the schema's extra_params field hints at a fallback (zabbix_raw_api_call), which is not part of this description.

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

Deploy Server