Skip to main content
Glama
mpeirone

zabbix-mcp-server

user_create

Create and configure new users in Zabbix by specifying username, password, user groups, and personal details. Returns JSON-formatted results for user creation.

Instructions

Create a new user in Zabbix.

Args:
    username: Username
    passwd: Password
    usrgrps: List of user groups (format: [{"usrgrpid": "1"}])
    name: First name
    surname: Last name
    email: Email address
    
Returns:
    str: JSON formatted creation result

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailNo
nameNo
passwdYes
surnameNo
usernameYes
usrgrpsYes

Implementation Reference

  • The handler function for the 'user_create' MCP tool. It is registered via the @mcp.tool() decorator and implements user creation in Zabbix using the ZabbixAPI. Includes type-hinted parameters serving as input schema, docstring documentation, read-only validation, parameter construction, API call, and JSON response formatting.
    @mcp.tool()
    def user_create(username: str, passwd: str, usrgrps: List[Dict[str, str]],
                    name: Optional[str] = None, surname: Optional[str] = None,
                    email: Optional[str] = None) -> str:
        """Create a new user in Zabbix.
        
        Args:
            username: Username
            passwd: Password
            usrgrps: List of user groups (format: [{"usrgrpid": "1"}])
            name: First name
            surname: Last name
            email: Email address
            
        Returns:
            str: JSON formatted creation result
        """
        validate_read_only()
        
        client = get_zabbix_client()
        params = {
            "username": username,
            "passwd": passwd,
            "usrgrps": usrgrps
        }
        
        if name:
            params["name"] = name
        if surname:
            params["surname"] = surname
        if email:
            params["email"] = email
        
        result = client.user.create(**params)
        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. While it states this is a creation operation, it doesn't mention authentication requirements, rate limits, whether the operation is idempotent, what happens on duplicate usernames, or any side effects. The description provides minimal behavioral context beyond the basic action.

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 well-structured with clear sections for the main purpose, arguments, and return value. It's appropriately sized with no redundant information, though the formatting could be slightly more polished. Every sentence serves a clear purpose in documenting the tool.

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?

For a creation tool with no annotations and no output schema, the description provides good parameter documentation but lacks important behavioral context. It explains what parameters to provide and the basic return format, but doesn't cover error conditions, authentication requirements, or system constraints that would be important for a user creation operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description provides excellent parameter semantics by clearly documenting all 6 parameters with brief explanations. It specifies the format for usrgrps ('[{"usrgrpid": "1"}]'), identifies required vs optional parameters through the Args section, and adds meaningful context beyond the bare schema titles.

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 tool creates a new user in Zabbix, providing a specific verb ('create') and resource ('user'). It distinguishes from siblings like user_get, user_update, and user_delete by focusing on creation, though it doesn't explicitly contrast with these alternatives.

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 like user_update or user_get. The description lacks context about prerequisites, permissions needed, or specific scenarios where user creation is appropriate versus other user management operations.

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