Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

User Update

user_update

Updates an existing Zabbix user account by changing only specified fields such as name, surname, password, or role.

Instructions

Update an existing user in Zabbix.

Modifies properties of an existing user account. You can change name, surname, password, or role. Only specify the fields you want to change.

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": {
      "userid": "<userid>"
    },
    "name": "user_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew first name.
passwdNoNew password.
roleidNoID of the user's role, which is what grants permissions. Roles are objects in Zabbix 5.2+; the old numeric user 'type' no longer exists.
useridYesID of the user to update.
surnameNoNew last name.
usernameNoNew username (not recommended - can cause issues).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.6.0
    • addedInput schema / properties / roleid
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "ID of the user's role, which is what grants permissions. Roles are objects in Zabbix 5.2+; the old numeric user 'type' no longer exists."
      +}
    • removedInput schema / properties / type_
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "integer"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": null,
      -  "description": "User type: 1=Zabbix user, 2=Zabbix admin, 3=Zabbix super admin."
      -}
  2. First observedv0.5.3

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is known. The description adds nothing beyond that: no mention of required permissions, what happens when a password or role is changed, or whether the operation can be reverted. It largely restates the name and annotations.

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?

Three short sentences, front-loaded with the core action and ending with the partial-update rule. The second sentence mostly restates the first, costing a little density but no real confusion.

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?

An output schema exists, so return values need not be explained, and the schema is fully documented. Still, for a user-account mutation an agent would benefit from knowing about permission requirements and side effects of password or role changes, which are absent.

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 each parameter is already documented in detail, including the caveat about username. The description's field list adds no syntax or constraint information beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource ('Update an existing user in Zabbix') and enumerates the mutable fields, so the tool's job is unambiguous. It stops short of naming sibling tools like user_create or user_delete, which the names make fairly obvious anyway.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Only specify the fields you want to change' usefully describes partial-update semantics and implies that userid is required and everything else optional. There is no explicit guidance on when to prefer this over user_create or on prerequisites such as admin permissions.

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