Skip to main content
Glama
Sign In
Zabbix MCP Server

Zabbix MCP Server

by initMAX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

autoregistration_get

Read-only

Fetch global Zabbix autoregistration settings to inspect the PSK identity, PSK key, and TLS accept mode used for automatic host registration.

Instructions

Get autoregistration settings. Returns the global configuration for automatic host registration: the PSK identity and key used for encrypted autoregistration, and the TLS accept mode. This is a singleton object with no filtering options.

Input Schema

NameRequiredDescriptionDefault
outputNoProperties of the autoregistration object to return. Pass 'extend' for all, or a list of property names. Default when omitted: 'extend'. Properties: tls_accept.
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.
extra_paramsNoOther native autoregistration.get parameters, merged into the request as-is. autoregistration.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": [
+        "tls_accept"
+      ],
+      "type": "string"
+    },
+    "minItems": 1,
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / output / description
      Previous value: -"Properties of the autoregistration 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: tls_accept."New value: +"Properties of the autoregistration object to return. Pass 'extend' for all, or a list of property names. Default when omitted: 'extend'. Properties: tls_accept."
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "autoregistration_getOutput",
-  "type": "object"
-}New value: +null
  2. First observedv1.41.0

TDQS

A4/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 the non-obvious behavioral fact that this returns sensitive credential material (PSK identity and key) plus the note that the object is a singleton, which sets expectations about cardinality. It does not describe the disclaimer preamble or the raw_json toggle, but that behavior is fully documented in the schema.

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?

Three short sentences, front-loaded with the action and result, then the returned fields, then the cardinality caveat. No filler and no repetition of schema detail.

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 zero-required-parameter, read-only singleton getter with no output schema, the description covers what an agent needs: what it reads, what comes back at a high level, and that no filtering is possible. A brief note on return shape or the untrusted-data wrapping would have made it complete.

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 parameters (output, server, raw_json, extra_params) are already well explained in the schema, including the enum values and the policy requirement for raw_json. The description's only added meaning is the assertion that no filtering parameters exist, which is useful but modest; baseline 3 applies.

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?

States a specific verb and resource ("Get autoregistration settings") and immediately enumerates the returned content: PSK identity, PSK key, and TLS accept mode. The clause "singleton object with no filtering options" differentiates it from the many filtered list-style *_get siblings in the toolset.

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?

Usage is implied by the resource name — read the global autoregistration configuration — but there is no explicit statement of when to prefer this over related configuration tools (authentication_get, settings_get, drule_get). The note that it is a singleton with no filtering does help an agent avoid passing filter arguments.

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