Skip to main content
Glama
Sign In
Zabbix MCP Server

Zabbix MCP Server

by initMAX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

device_get

Read-only

Retrieve paired Zabbix mobile app devices and filter them by device, user, role, or user group to inspect ownership, status, activation, and last access.

Instructions

Retrieve paired mobile devices (Zabbix 8.0+): the Zabbix mobile app installations that users onboarded, with the owning userid, device name, status, activated_at and lastaccess. Filter by deviceids, userids, roleids or usrgrpids. Use device_offboard to revoke a device.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of records to return.
filterNoReturn only results whose properties exactly match the given values (a single value or a list of values per key). Example: {"status": 0} or {"status": [0, 1]}. Keys: activated_at, deviceid, enrollment_token_expires_at, lastaccess, name, status, userid, uuid. Text properties cannot be filtered; use 'search' for them.
outputNoProperties of the device object to return. Pass 'extend' for all, 'count' for the number of matches only, or a list of property names. Default when omitted: deviceid, userid, name, status, lastaccess. Properties: activated_at, deviceid, enrollment_token_expires_at, lastaccess, name, status, userid, uuid.
searchNoReturn results whose string properties contain the given pattern (case-insensitive; '*' is a wildcard when searchWildcardsEnabled is true). Example: {"name": "web"}. Keys: name, uuid.
serverNoTarget Zabbix server. Available: default. Defaults to 'default' if omitted.
roleidsNoReturn only devices belonging to users with the given roles.
useridsNoReturn only devices belonging to the given users.
raw_jsonNoStrips the security disclaimer preamble from the response so it is pure JSON. Default: false. Requires the bearer token to have 'allow_raw_json' explicitly enabled by an operator in the admin portal - tokens without that policy receive a PolicyError instead. WARNING: setting true bypasses the prompt-injection mitigation marker that wraps untrusted Zabbix data (host names, item descriptions, problem text). LLM clients (Claude, GPT, Cursor, ...) should leave this false; only programmatic non-LLM consumers (Python scripts, n8n workflows that json.loads the result) should set true.
deviceidsNoReturn only devices with the given IDs.
sortfieldNoSort by one or more of: deviceid, name (a list for several; pair with 'sortorder'). No other property is sortable.
sortorderNoSort order: 'ASC' or 'DESC'.
usrgrpidsNoReturn only devices belonging to users in the given user groups.
countOutputNoReturn the count of matching devices instead of the records.
extra_paramsNoOther native device.get parameters, merged into the request as-is. device.get has no parameters beyond the typed ones. Any other key is refused here, because Zabbix would silently ignore it. For a parameter you are sure exists on your release but is not listed, use zabbix_raw_api_call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv1.42.2
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / extra_params / anyOf
      Previous value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "propertyNames": {
+      "enum": [
+        "excludeSearch",
+        "preservekeys",
+        "searchByAny",
+        "searchWildcardsEnabled",
+        "startSearch"
+      ]
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / filter / anyOf
      Previous value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "propertyNames": {
+      "enum": [
+        "activated_at",
+        "deviceid",
+        "enrollment_token_expires_at",
+        "lastaccess",
+        "name",
+        "status",
+        "userid",
+        "uuid"
+      ]
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / filter / description
      Previous value: -"Return only results whose properties exactly match the given values (a single value or a list of values per key). Example: {\"status\": 0} or {\"status\": [0, 1]}. Keys: activated_at, deviceid, lastaccess, name, status, userid, uuid. Text properties cannot be filtered; use 'search' for them."New value: +"Return only results whose properties exactly match the given values (a single value or a list of values per key). Example: {\"status\": 0} or {\"status\": [0, 1]}. Keys: activated_at, deviceid, enrollment_token_expires_at, lastaccess, name, status, userid, uuid. Text properties cannot be filtered; use 'search' for them."
    • changedInput schema / properties / output / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "extend",
+      "count"
+    ],
+    "type": "string"
+  },
+  {
+    "items": {
+      "enum": [
+        "activated_at",
+        "deviceid",
+        "enrollment_token_expires_at",
+        "lastaccess",
+        "name",
+        "status",
+        "userid",
+        "uuid"
+      ],
+      "type": "string"
+    },
+    "minItems": 1,
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / output / description
      Previous value: -"Properties of the device object to return. Pass 'extend' for all, 'count' for the number of matches only, or a comma-separated list of property names. Default when omitted: deviceid, userid, name, status, lastaccess. Properties: activated_at, deviceid, lastaccess, name, status, userid, uuid."New value: +"Properties of the device object to return. Pass 'extend' for all, 'count' for the number of matches only, or a list of property names. Default when omitted: deviceid, userid, name, status, lastaccess. Properties: activated_at, deviceid, enrollment_token_expires_at, lastaccess, name, status, userid, uuid."
    • changedInput schema / properties / search / anyOf
      Previous value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "propertyNames": {
+      "enum": [
+        "name",
+        "uuid"
+      ]
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / sortfield / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "deviceid",
+      "name"
+    ],
+    "type": "string"
+  },
+  {
+    "items": {
+      "enum": [
+        "deviceid",
+        "name"
+      ],
+      "type": "string"
+    },
+    "minItems": 1,
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / sortfield / description
      Previous value: -"Sort by one or more of: deviceid, name (comma-separated for several; pair with 'sortorder'). No other property is sortable."New value: +"Sort by one or more of: deviceid, name (a list for several; pair with 'sortorder'). No other property is sortable."
    • changedInput schema / properties / sortorder / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "ASC",
+      "DESC"
+    ],
+    "type": "string"
+  },
+  {
+    "items": {
+      "enum": [
+        "ASC",
+        "DESC"
+      ],
+      "type": "string"
+    },
+    "minItems": 1,
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "device_getOutput",
-  "type": "object"
-}New value: +null
  2. First observedv1.41.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish this as a safe read (readOnlyHint true, openWorldHint false), so the description only needs to add context — and it does, adding the Zabbix 8.0+ version gate and enumerating the returned attributes. The remaining caveats (raw_json policy, truncation/limit behavior) are deferred entirely to the schema rather than reinforced here.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences: identity and definition first, returned fields second, filtering third, alternative tool last. Every phrase carries information and nothing is padded.

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?

For a 14-parameter but fully documented read tool with no output schema, the description usefully compensates by listing the default returned fields and the version prerequisite. It deliberately omits pagination, count and output-shaping behavior, which the rich schema covers.

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 coverage is 100%, so every parameter including filter, output, limit, sort and extra_params is already documented. The description only restates four filter shortcuts (deviceids, userids, roleids, usrgrpids) that the schema spells out in more detail, adding no new syntax or constraint information.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Uses a specific verb ('Retrieve') plus a precisely defined resource: paired mobile devices, explicitly glossed as 'Zabbix mobile app installations that users onboarded'. It further names the returned fields (userid, name, status, activated_at, lastaccess), so an agent knows exactly which endpoint semantics this is, distinct from the many other *_get siblings.

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

Usage Guidelines4/5

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

Gives clear retrieval context and routes the agent away from a write path with 'Use device_offboard to revoke a device'. It does not, however, contrast against competing read tools (e.g. user_get for ownership data), so the when-to-use guidance is solid but not exhaustive.

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

Deploy Server

Other Tools