Skip to main content
Glama
mpeirone

zabbix-mcp-server

trigger_get

Retrieve Zabbix triggers with flexible filtering by trigger, host, group, or template IDs, and customize output in JSON format for precise monitoring data extraction.

Instructions

Get triggers from Zabbix with optional filtering.

Args:
    triggerids: List of trigger IDs to retrieve
    hostids: List of host IDs to filter by
    groupids: List of host group IDs to filter by
    templateids: List of template IDs to filter by
    output: Output format
    search: Search criteria
    filter: Filter criteria
    limit: Maximum number of results
    
Returns:
    str: JSON formatted list of triggers

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filterNo
groupidsNo
hostidsNo
limitNo
outputNoextend
searchNo
templateidsNo
triggeridsNo

Implementation Reference

  • The trigger_get tool handler: decorated with @mcp.tool() which registers it with FastMCP, implements retrieval of Zabbix triggers via API with filtering options, formats response as JSON.
    @mcp.tool()
    def trigger_get(triggerids: Optional[List[str]] = None,
                    hostids: Optional[List[str]] = None,
                    groupids: Optional[List[str]] = None,
                    templateids: Optional[List[str]] = None,
                    output: Union[str, List[str]] = "extend",
                    search: Optional[Dict[str, str]] = None,
                    filter: Optional[Dict[str, Any]] = None,
                    limit: Optional[int] = None) -> str:
        """Get triggers from Zabbix with optional filtering.
        
        Args:
            triggerids: List of trigger IDs to retrieve
            hostids: List of host IDs to filter by
            groupids: List of host group IDs to filter by
            templateids: List of template IDs to filter by
            output: Output format (extend or list of specific fields)
            search: Search criteria
            filter: Filter criteria
            limit: Maximum number of results
            
        Returns:
            str: JSON formatted list of triggers
        """
        client = get_zabbix_client()
        params = {"output": output}
        
        if triggerids:
            params["triggerids"] = triggerids
        if hostids:
            params["hostids"] = hostids
        if groupids:
            params["groupids"] = groupids
        if templateids:
            params["templateids"] = templateids
        if search:
            params["search"] = search
        if filter:
            params["filter"] = filter
        if limit:
            params["limit"] = limit
        
        result = client.trigger.get(**params)
        return format_response(result)
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states it 'Get triggers' and returns 'JSON formatted list of triggers,' which implies a read-only operation, but doesn't cover critical aspects like authentication needs, rate limits, error handling, or pagination behavior. For a tool with 8 parameters and no annotations, this is insufficient.

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 and concise, with a clear purpose statement followed by parameter and return sections. Every sentence serves a purpose, though the parameter list is brief and could be more informative. It's front-loaded and avoids unnecessary details, making it efficient.

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

Completeness2/5

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

Given the complexity (8 parameters, no annotations, no output schema), the description is incomplete. It covers the basic purpose and lists parameters but lacks usage guidelines, behavioral details, and output specifics. For a data retrieval tool in a system like Zabbix, more context on filtering logic and result handling is needed.

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?

The description lists all 8 parameters with brief labels, adding minimal semantics beyond the schema's titles. Since schema description coverage is 0%, the description compensates slightly by naming parameters, but it doesn't explain their purposes, formats, or interactions (e.g., how 'filter' differs from 'search'). This meets the baseline for partial compensation but lacks depth.

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 tool's purpose: 'Get triggers from Zabbix with optional filtering.' This specifies the verb ('Get'), resource ('triggers'), and system ('Zabbix'), making the function unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'trigger_create' or 'trigger_update' beyond the 'Get' verb, which is why it doesn't reach a perfect score.

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. It mentions 'optional filtering' but doesn't specify scenarios, prerequisites, or comparisons to other tools like 'problem_get' or 'event_get' for related data. This leaves the agent without context for tool selection.

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