Skip to main content
Glama
mpeirone

zabbix-mcp-server

trigger_update

Update Zabbix triggers by modifying description, expression, priority, or status using trigger ID. Returns JSON-formatted results for streamlined monitoring adjustments.

Instructions

Update an existing trigger in Zabbix.

Args:
    triggerid: Trigger ID to update
    description: New trigger description
    expression: New trigger expression
    priority: New severity level
    status: New status (0=enabled, 1=disabled)
    
Returns:
    str: JSON formatted update result

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
descriptionNo
expressionNo
priorityNo
statusNo
triggeridYes

Implementation Reference

  • The handler function for the 'trigger_update' tool, decorated with @mcp.tool() which also serves as registration. It updates a Zabbix trigger using the ZabbixAPI client, validating read-only mode first.
    @mcp.tool()
    def trigger_update(triggerid: str, description: Optional[str] = None,
                       expression: Optional[str] = None, priority: Optional[int] = None,
                       status: Optional[int] = None) -> str:
        """Update an existing trigger in Zabbix.
        
        Args:
            triggerid: Trigger ID to update
            description: New trigger description
            expression: New trigger expression
            priority: New severity level
            status: New status (0=enabled, 1=disabled)
            
        Returns:
            str: JSON formatted update result
        """
        validate_read_only()
        
        client = get_zabbix_client()
        params = {"triggerid": triggerid}
        
        if description:
            params["description"] = description
        if expression:
            params["expression"] = expression
        if priority is not None:
            params["priority"] = priority
        if status is not None:
            params["status"] = status
        
        result = client.trigger.update(**params)
        return format_response(result)
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 only states it's an update operation. Missing critical behavioral details: whether this requires specific permissions, if changes are reversible, what happens to unspecified fields, rate limits, or error conditions. The description adds minimal value beyond the basic operation type.

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?

Well-structured with clear sections (Args, Returns), front-loaded purpose statement, and efficient parameter explanations. The status mapping is particularly helpful. Could be slightly more concise by integrating parameter details more seamlessly, but overall efficient.

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?

For a mutation tool with 5 parameters, 0% schema coverage, and no output schema, the description provides adequate parameter semantics but lacks behavioral context. It mentions the return format ('JSON formatted update result') which helps, but doesn't describe what success/failure responses look like or operational constraints.

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 provides meaningful parameter documentation: explains triggerid is required, describes each field's purpose, and includes status mapping (0=enabled, 1=disabled). This significantly compensates for the schema gap, though it doesn't cover all potential edge cases or format requirements.

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 'Update an existing trigger in Zabbix' - a specific verb ('Update') with resource ('trigger'), and distinguishes from sibling tools like trigger_create, trigger_delete, and trigger_get. However, it doesn't explicitly differentiate from other update tools like host_update or template_update beyond the resource type.

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 implies usage context through the parameter documentation (requires triggerid, updates specific fields), but doesn't explicitly state when to use this vs. trigger_create or trigger_delete. No guidance on prerequisites, permissions, or alternative approaches is provided.

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