Skip to main content
Glama
mpeirone

zabbix-mcp-server

problem_get

Retrieve and filter problems from Zabbix by event IDs, host groups, severity levels, or time range. Returns JSON-formatted data for efficient monitoring and issue tracking.

Instructions

Get problems from Zabbix with optional filtering.

Args:
    eventids: List of event IDs to retrieve
    groupids: List of host group IDs to filter by
    hostids: List of host IDs to filter by
    objectids: List of object IDs to filter by
    output: Output format
    time_from: Start time (Unix timestamp)
    time_till: End time (Unix timestamp)
    recent: Only recent problems
    severities: List of severity levels to filter by
    limit: Maximum number of results
    
Returns:
    str: JSON formatted list of problems

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eventidsNo
groupidsNo
hostidsNo
limitNo
objectidsNo
outputNoextend
recentNo
severitiesNo
time_fromNo
time_tillNo
Behavior2/5

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

With no annotations provided, the description carries full burden but lacks behavioral details. It doesn't disclose whether this is a read-only operation, potential rate limits, authentication needs, or how errors are handled. The mention of 'JSON formatted list' in returns adds minimal context but insufficient for a mutation-aware tool.

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 well-structured with a clear opening sentence followed by categorized Args and Returns sections. It's appropriately sized with no redundant information, though the parameter explanations could be slightly more detailed without losing efficiency.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 10 parameters with 0% schema coverage and no output schema, the description does a decent job by listing parameters and stating the return format. However, for a tool with many optional filters and no annotations, it lacks details on default behaviors, error cases, or example usage, leaving gaps in completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description compensates by listing all 10 parameters with brief explanations (e.g., 'List of event IDs to retrieve', 'Start time (Unix timestamp)'). This adds significant meaning beyond the bare schema, though some details like format specifics for 'output' are still vague.

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 description clearly states the verb ('Get') and resource ('problems from Zabbix'), and mentions optional filtering. However, it doesn't explicitly differentiate from sibling tools like 'event_get' or 'trigger_get' that might also retrieve related data, missing full sibling differentiation.

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 guidance on when to use this tool versus alternatives like 'event_get' or 'trigger_get', nor does it mention prerequisites or specific contexts for usage. It only states the basic function without comparative advice.

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

Related 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/mpeirone/zabbix-mcp-server'

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