Skip to main content
Glama
mpeirone

zabbix-mcp-server

by mpeirone
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

trigger_delete

Remove specified triggers from Zabbix by providing trigger IDs. Returns deletion results in JSON format for easy integration and tracking.

Instructions

Delete triggers from Zabbix.

Args:
    triggerids: List of trigger IDs to delete
    
Returns:
    str: JSON formatted deletion result

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
triggeridsYes

Implementation Reference

  • src/zabbix_mcp_server.py:576-590 (handler)
    The main handler function for the 'trigger_delete' tool. It is decorated with @mcp.tool() which handles registration in FastMCP. The function checks read-only mode, authenticates with Zabbix API via get_zabbix_client(), calls the Zabbix trigger.delete API method, and formats the response as JSON.
    @mcp.tool()
def trigger_delete(triggerids: List[str]) -> str:
    """Delete triggers from Zabbix.
    
    Args:
        triggerids: List of trigger IDs to delete
        
    Returns:
        str: JSON formatted deletion result
    """
    validate_read_only()
    
    client = get_zabbix_client()
    result = client.trigger.delete(*triggerids)
    return format_response(result)

Tool Definition Quality

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool deletes triggers, implying a destructive mutation, but lacks details on permissions required, whether deletion is permanent/reversible, rate limits, or error handling. The mention of a JSON-formatted result adds some value, but overall behavioral context is minimal.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is highly concise and well-structured: a clear purpose statement followed by Args and Returns sections. Every sentence adds value without redundancy, making it easy to parse and understand quickly.

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 the tool's complexity (destructive deletion with no annotations, 1 parameter, no output schema), the description is minimally adequate. It covers the basic action and parameter but lacks critical details like side effects, permissions, or output structure beyond 'JSON formatted.' For a deletion tool, more completeness is expected to ensure safe use.

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?

The description adds meaningful context beyond the input schema. The schema only defines 'triggerids' as an array of strings, but the description clarifies it's a 'List of trigger IDs to delete,' specifying the parameter's purpose. With 0% schema description coverage and 1 parameter, this compensates adequately, though it doesn't detail ID format or constraints.

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 action ('Delete') and resource ('triggers from Zabbix'), making the purpose unambiguous. It distinguishes itself from sibling tools like trigger_get, trigger_create, and trigger_update by specifying deletion. However, it doesn't explicitly differentiate from other deletion tools like host_delete or template_delete 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., trigger existence), consequences, or when to choose deletion over other operations like deactivation or updates. It simply states what it does without context.

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