Skip to main content
Glama
mpeirone

zabbix-mcp-server

hostgroup_create

Create a new host group in Zabbix by specifying the group name, enabling organized monitoring and management of devices within the Zabbix-MCP server.

Instructions

Create a new host group in Zabbix.

Args:
    name: Host group name
    
Returns:
    str: JSON formatted creation result

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes

Implementation Reference

  • The 'hostgroup_create' tool handler function. Decorated with @mcp.tool() for registration in FastMCP. Validates read-only mode, authenticates Zabbix client if needed, calls the Zabbix API hostgroup.create method with the provided name, and returns formatted JSON response.
    @mcp.tool()
    def hostgroup_create(name: str) -> str:
        """Create a new host group in Zabbix.
        
        Args:
            name: Host group name
            
        Returns:
            str: JSON formatted creation result
        """
        validate_read_only()
        
        client = get_zabbix_client()
        result = client.hostgroup.create(name=name)
        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 for behavioral disclosure. It states the tool creates something but doesn't mention permissions required, whether this is a safe operation, potential side effects, rate limits, or what the 'JSON formatted creation result' contains. This leaves significant behavioral gaps for a mutation tool.

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 and front-loaded with the core purpose in the first sentence. The Args/Returns sections are structured but could be more integrated. There's minimal waste, though the 'JSON formatted' detail might be redundant if an output schema existed.

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 this is a mutation tool with no annotations, no output schema, and low schema coverage, the description is incomplete. It doesn't explain what a 'host group' is in Zabbix context, what the creation result contains, error conditions, or dependencies, leaving the agent with insufficient context for reliable 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?

The description adds minimal parameter semantics beyond the input schema. It documents that 'name' is the 'Host group name', which matches the schema's title 'Name', but with 0% schema description coverage, this doesn't fully compensate. The baseline is 3 since the description provides basic mapping but lacks details like format constraints or examples.

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 ('Create a new host group') and resource ('in Zabbix'), which provides specific verb+resource information. However, it doesn't differentiate from sibling tools like hostgroup_update or hostgroup_delete, which would require explicit comparison to achieve 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?

No guidance is provided on when to use this tool versus alternatives. The description lacks context about prerequisites, when this operation is appropriate, or comparisons to sibling tools like hostgroup_get or hostgroup_update, leaving the agent without usage direction.

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