Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

User Create

user_create

Create a Zabbix user account with credentials, role, and group memberships to grant login access and permissions.

Instructions

Create a new user in Zabbix.

Creates a new user account with specified credentials, role and group membership.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "username": "<username>",
      "passwd": "<passwd>",
      "usrgrps": "<usrgrps>"
    },
    "name": "user_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoUser's first name (optional).
passwdYesPassword.
roleidNoID of the user's role, which is what grants permissions. Defaults to '1' (User role); a user created without one gets roleid 0 and cannot log in.1
surnameNoUser's last name (optional).
usrgrpsYesUser groups [{'usrgrpid': '1'}].
usernameYesUsername.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.0
    • addedInput schema / properties / roleid
      Added value: +{
      +  "default": "1",
      +  "description": "ID of the user's role, which is what grants permissions. Defaults to '1' (User role); a user created without one gets roleid 0 and cannot log in.",
      +  "type": "string"
      +}
  2. First observedv0.5.3

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the safety profile is covered. The description adds that it creates a user account with credentials, role, and group membership, but does not disclose duplicate-username behavior, permission requirements, or authentication implications beyond what the schema provides.

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 short and front-loaded with the core action. The second sentence partially restates the first but does add the account-composition details, so there is minor redundancy rather than verbosity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has rich structured context: 100% schema description coverage, annotations covering mutation safety, and an output schema. Given that support, the description is sufficient to identify the tool as a user-creation operation, though it could mention duplicate handling or required group semantics more explicitly.

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 100%, so the schema already documents all parameters in detail. The description maps at a high level to credentials, role, and group membership, but adds no syntax, format, or default-value information beyond the schema.

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 uses a specific verb and resource: "Create a new user in Zabbix." It also clarifies that the created account includes credentials, role, and group membership. It does not explicitly distinguish itself from siblings like user_update or user_delete, but the create purpose is unambiguous.

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 states what the tool does but gives no guidance on when to use it versus alternatives such as user_update or user_get. It also omits prerequisites, exclusions, or warnings about duplicate usernames.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.