Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

User Get

user_get
Read-onlyIdempotent

Retrieve Zabbix users with optional filters, IDs, sorting, and pagination to inspect accounts and permissions.

Instructions

Get users from Zabbix.

Users represent people with access to the Zabbix system. Each user has authentication credentials and permission level determining what they can view and modify.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "user_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return. Default is 100.
offsetNoNumber of matching records to skip. Use with 'limit' to page through results; check 'has_more' and 'total' in the response.
outputNoextend
searchNoDictionary with search criteria like {'username': 'admin'}. Zabbix 5.4 renamed 'alias' to 'username' and rejects the old name.
useridsNoList of user IDs to get. Omit to return all users; an empty list matches none.
sortfieldNoField to sort by. A deterministic sort is required for paging to be consistent.userid
sortorderNoSort direction - 'ASC' or 'DESC'.ASC
count_outputNoIf true, returns only the count of matched objects as an integer.
filter_paramsNoAdditional filter parameters for advanced filtering.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.7.1
    • changedInput schema / properties / userids / description
      Previous value: -"List of user IDs to get. If empty, returns all users."New value: +"List of user IDs to get. Omit to return all users; an empty list matches none."
  2. Changed6 schema fields changedv0.6.0
    • changedInput schema / properties / offset / description
      Previous value: -"Number of results to skip (for pagination). Requires sortfield to be set."New value: +"Number of matching records to skip. Use with 'limit' to page through results; check 'has_more' and 'total' in the response."
    • changedInput schema / properties / search / description
      Previous value: -"Dictionary with search criteria like {'alias': 'admin'} for username matching."New value: +"Dictionary with search criteria like {'username': 'admin'}. Zabbix 5.4\n    renamed 'alias' to 'username' and rejects the old name."
    • removedInput schema / properties / sortfield / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • changedInput schema / properties / sortfield / default
      Previous value: -nullNew value: +"userid"
    • changedInput schema / properties / sortfield / description
      Previous value: -"Field to sort by."New value: +"Field to sort by. A deterministic sort is required for paging to be consistent."
    • addedInput schema / properties / sortfield / type
      Added value: +"string"
  3. 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=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds domain context about what Zabbix users represent, but does not disclose additional behavior such as pagination, filtering behavior, or authentication requirements.

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-loads the core action: 'Get users from Zabbix.' The second sentence adds useful domain context but is not operationally necessary for invoking the tool.

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?

Given the rich input schema, output schema, and read-only/idempotent annotations, the description is largely complete for a retrieval tool. It establishes the resource and its meaning, though it omits usage guidance and does not mention filtering or paging behavior already covered by the schema.

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 high at 89%, so the schema already documents most parameters. The description does not add any parameter-level meaning beyond what the schema provides, which is the baseline expectation when schema coverage is high.

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 states a specific verb and resource: 'Get users from Zabbix.' It clearly identifies the user entity and its domain meaning, but does not explicitly differentiate this retrieval tool from sibling user tools such as user_create, user_update, or user_delete.

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 gives no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. Usage is only implied by the verb 'Get' and the resource 'users'.

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