Skip to main content
Glama
mpeirone

zabbix-mcp-server

item_delete

Remove items from Zabbix by specifying item IDs. Provides JSON-formatted results for deletion confirmation, streamlining item management in monitoring systems.

Instructions

Delete items from Zabbix.

Args:
    itemids: List of item IDs to delete
    
Returns:
    str: JSON formatted deletion result

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemidsYes

Implementation Reference

  • The main handler function for the 'item_delete' tool. It is decorated with @mcp.tool() which registers it as an MCP tool. The function deletes the specified items using the Zabbix API client and returns a formatted JSON response. It checks read-only mode before performing the deletion.
    @mcp.tool()
    def item_delete(itemids: List[str]) -> str:
        """Delete items from Zabbix.
        
        Args:
            itemids: List of item IDs to delete
            
        Returns:
            str: JSON formatted deletion result
        """
        validate_read_only()
        
        client = get_zabbix_client()
        result = client.item.delete(*itemids)
        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 the full burden of behavioral disclosure. It states the action is a deletion but doesn't mention critical details like permissions required, whether deletion is permanent or reversible, rate limits, or error handling. This is inadequate for a destructive operation.

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 brief, bullet-like sections for Args and Returns. Every sentence adds value without redundancy, making it efficient and front-loaded.

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 tool's destructive nature, lack of annotations, and no output schema, the description is incomplete. It fails to address safety concerns, return value details beyond format, or error scenarios, which are crucial for a deletion tool in this context.

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 for the single parameter 'itemids' by specifying it as a 'List of item IDs to delete', which clarifies its purpose beyond the schema's basic type definition. With 0% schema description coverage, this compensates well, though it doesn't detail ID formats 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 ('items from Zabbix'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'host_delete' or 'template_delete' beyond specifying the resource type, missing explicit sibling distinction.

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 lacks context about prerequisites (e.g., item existence), exclusions, or comparisons to other deletion tools in the sibling list, leaving usage unclear.

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