Skip to main content
Glama
mpeirone

zabbix-mcp-server

by mpeirone
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

host_delete

Remove hosts from Zabbix monitoring by specifying host IDs. Returns a JSON-formatted result confirming successful deletions for efficient system management.

Instructions

Delete hosts from Zabbix.

Args:
    hostids: List of host IDs to delete
    
Returns:
    str: JSON formatted deletion result

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostidsYes

Implementation Reference

  • src/zabbix_mcp_server.py:223-237 (handler)
    The host_delete tool handler, decorated with @mcp.tool() for MCP registration. It validates read-only mode, gets the Zabbix client, deletes the specified hosts using the Zabbix API, and returns a formatted JSON response.
    @mcp.tool()
def host_delete(hostids: List[str]) -> str:
    """Delete hosts from Zabbix.
    
    Args:
        hostids: List of host IDs to delete
        
    Returns:
        str: JSON formatted deletion result
    """
    validate_read_only()
    
    client = get_zabbix_client()
    result = client.host.delete(*hostids)
    return format_response(result)

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Delete' implies a destructive operation, the description doesn't mention critical behavioral aspects like whether deletion is permanent, requires specific permissions, affects related resources, or has rate limits. The return format is mentioned but not the content or error behavior.

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 appropriately sized with three sentences that each serve a purpose: stating the action, explaining the parameter, and describing the return format. It's front-loaded with the core purpose. Minor improvement could be made by integrating the parameter explanation more seamlessly.

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?

For a destructive operation with no annotations and no output schema, the description is insufficient. It doesn't cover critical context like deletion consequences, permissions needed, error handling, or relationship to other tools. The return format mention is helpful but doesn't compensate for missing behavioral transparency.

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?

Schema description coverage is 0%, so the description must compensate. It does explain the single parameter ('List of host IDs to delete'), which adds meaning beyond the bare schema. However, it doesn't provide format examples, validation rules, or what happens with invalid IDs, leaving some semantic gaps.

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 ('hosts from Zabbix'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from other deletion tools like hostgroup_delete, template_delete, or user_delete, which would require sibling differentiation for a score of 5.

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. There are multiple deletion tools in the sibling list (hostgroup_delete, template_delete, user_delete, etc.), but no indication of when host deletion is appropriate versus other deletion operations or when to use host_update instead.

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