Skip to main content
Glama
mpeirone

zabbix-mcp-server

by mpeirone
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

hostgroup_delete

Remove specified host groups from Zabbix by providing their group IDs. Returns a JSON-formatted result confirming the deletion process.

Instructions

Delete host groups from Zabbix.

Args:
    groupids: List of group IDs to delete
    
Returns:
    str: JSON formatted deletion result

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupidsYes

Implementation Reference

  • src/zabbix_mcp_server.py:306-320 (handler)
    The handler function for the hostgroup_delete tool. It checks if the server is in read-only mode, retrieves the Zabbix API client, calls the hostgroup.delete method with the provided groupids, and returns a JSON-formatted response.
    @mcp.tool()
def hostgroup_delete(groupids: List[str]) -> str:
    """Delete host groups from Zabbix.
    
    Args:
        groupids: List of group IDs to delete
        
    Returns:
        str: JSON formatted deletion result
    """
    validate_read_only()
    
    client = get_zabbix_client()
    result = client.hostgroup.delete(*groupids)
    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 but only states it deletes host groups and returns a JSON result. It lacks critical behavioral details: whether deletion is irreversible, requires specific permissions, affects associated hosts or items, has rate limits, or what the JSON output contains (e.g., success/failure status). 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.

Conciseness4/5

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

The description is front-loaded with the core action and uses a structured format (Args/Returns). It's efficient with minimal waste, though the 'Returns' line could be more informative (e.g., 'JSON with deletion status') to enhance clarity without adding bulk.

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 tool with no annotations, 0% schema coverage, and no output schema, the description is incomplete. It misses essential context: irreversible nature, permissions, impact on related entities, error handling, and output details. This leaves the agent under-informed for safe and effective use.

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 adds that 'groupids' are 'List of group IDs to delete', clarifying the parameter's purpose beyond the schema's array of strings. However, it doesn't explain ID format, sourcing (e.g., from 'hostgroup_get'), or validation rules, leaving gaps in understanding.

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 verb ('Delete') and resource ('host groups from Zabbix'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'host_delete' or 'template_delete', which would require mentioning it specifically targets host groups rather than individual hosts or templates.

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. It doesn't mention prerequisites (e.g., host groups must exist, be empty), exclusions (e.g., cannot delete default groups), or related tools like 'hostgroup_get' for verification, leaving the agent to infer usage from context alone.

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