Skip to main content
Glama
mhajder

Zabbix MCP Server

by mhajder

problem_get

Read-onlyIdempotent

Retrieve active problems from Zabbix monitoring. Filter by severity, host, or time to identify infrastructure issues needing attention.

Instructions

Get problems from Zabbix.

Problems are active trigger states that indicate issues with monitored infrastructure. Each problem is associated with a trigger and can be acknowledged by operators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return. Default is 100.
offsetNoNumber of results to skip (for pagination). Requires sortfield to be set.
outputNoextend
recentNoIf true, only return recently recovered problems.
searchNoDictionary with search criteria like {'name': 'CPU'}.
hostidsNoList of host IDs to get problems from.
eventidsNoList of event IDs to get problems for. If empty, returns all problems.
groupidsNoList of host group IDs to get problems from.
objectidsNoList of trigger IDs to get problems from.
sortfieldNoField to sort by.
sortorderNoSort direction - 'ASC' or 'DESC'.ASC
time_fromNoUnix timestamp.
time_tillNoUnix timestamp.
severitiesNoSeverity levels 0-5.
suppressedNoIf false, return only unsuppressed problems. If true, return only suppressed problems.
acknowledgedNoIf false, return only unacknowledged problems. If true, return only acknowledged problems.
count_outputNoIf true, returns only the count of matched objects as an integer.
name_containsNoShortcut to search for problems by name (constructs search={'name': name_contains}).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds context about problems being associated with triggers and acknowledgable, but does not significantly extend behavioral disclosure beyond annotations.

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 description is concise with three sentences, no redundant information. Could be slightly more structured but efficient overall.

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?

Given 18 parameters, rich schema, and annotations, the description provides adequate high-level context. It does not detail all filtering logic but complements the structured data well.

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 coverage is 94%, so the schema already describes parameters well. The description does not add parameter-specific semantics beyond a high-level overview, meeting the baseline for high coverage.

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 clearly states the verb 'Get' and resource 'problems', and defines problems as active trigger states indicating issues. It differentiates from siblings by emphasizing the problem domain, distinct from triggers or events.

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?

The description explains what problems are but does not explicitly state when to use this tool versus alternatives like trigger_get or event_get. Usage context is implied but not explicitly contrasted.

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