Skip to main content
Glama
Sign In
Zabbix MCP Server

Zabbix MCP Server

by initMAX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

serverinfo_get

Read-only

Retrieve a Zabbix server's UUID and last access time to verify server identity and check recent database activity.

Instructions

Retrieve information about a Zabbix server instance (Zabbix 8.0+): its serverid and lastaccess, the time of its last update to the database (for an HA cluster the active node's). serverid is required: the server's UUIDv7, returned as 'serverid' by settings_get (8.0+) and shown in the frontend under Reports / System information. For the API version use apiinfo_version, for HA nodes hanode_get, for queue and status health_check.

Input Schema

NameRequiredDescriptionDefault
outputNoProperties of the serverinfo object to return. Pass 'extend' for all, or a list of property names. Default when omitted: 'extend'. Properties: lastaccess, serverid.
serverNoTarget Zabbix server. Available: default. Defaults to 'default' if omitted.
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.
serveridYesID (UUID) of the Zabbix server to describe.
extra_paramsNoOther native serverinfo.get parameters, merged into the request as-is. serverinfo.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. Changed5 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: +[
+  {
+    "additionalProperties": false,
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / output / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "extend"
+    ],
+    "type": "string"
+  },
+  {
+    "items": {
+      "enum": [
+        "lastaccess",
+        "serverid"
+      ],
+      "type": "string"
+    },
+    "minItems": 1,
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / output / description
      Previous value: -"Properties of the serverinfo 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: 'extend'. Properties: lastaccess, serverid."New value: +"Properties of the serverinfo object to return. Pass 'extend' for all, or a list of property names. Default when omitted: 'extend'. Properties: lastaccess, serverid."
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "serverinfo_getOutput",
-  "type": "object"
-}New value: +null
  2. First observedv1.41.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds meaningful behavior beyond that, namely the 8.0+ version requirement and the fact that in an HA cluster the lastaccess value reflects the active node. It does not describe response framing or error behavior, but with annotations carrying the safety story that is a minor gap.

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?

Two dense sentences with the purpose and returned fields front-loaded, followed by the sibling routing rule; nothing is decorative. It is at the upper edge of comfortable length, and the parenthetical version tag could be integrated more smoothly, but no sentence is wasted.

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?

There is no output schema, and the description compensates by naming exactly what the call returns (serverid, lastaccess) and clarifying the HA interpretation of lastaccess. Combined with the version gate and the serverid provenance, an agent has everything needed to call it correctly; only response envelope details are absent.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline would be 3, but the description adds real meaning for the one required parameter: serverid is a UUIDv7 and is obtainable from settings_get or the frontend. The remaining parameters (output, server, raw_json, extra_params) are left to their already-thorough schema descriptions rather than restated.

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?

The description gives a specific verb and resource ('Retrieve information about a Zabbix server instance') and immediately names the returned fields, serverid and lastaccess, plus the version gate (8.0+). It also explicitly distinguishes itself from apiinfo_version, hanode_get and health_check, so an agent can pick it out of a 70-tool sibling list without opening the schema.

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

Usage Guidelines5/5

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

It states both when to use this tool and which sibling to use instead for adjacent needs: API version goes to apiinfo_version, HA node data to hanode_get, queue and status to health_check. It also removes the biggest selection blocker by telling the agent where serverid comes from (settings_get 8.0+ or the frontend under Reports / System information).

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