Skip to main content
Glama
initMAX

Zabbix MCP Server

by initMAX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

autoregistration_get

Read-only

Retrieve global Zabbix autoregistration settings, including PSK identity, encryption key, and TLS accept mode, to verify automatic host registration configuration.

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

TableJSON Schema
NameRequiredDescriptionDefault
outputNoProperties 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.
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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 and openWorldHint, so the safety profile is partly covered. The description adds real value beyond them: it identifies the object as a global singleton, notes the absence of filtering, and discloses that the response contains sensitive material (PSK identity and key). It stops short of stating any permission/auth requirement for that sensitive read.

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 tight sentences: purpose, contents, and the singleton/no-filter constraint. Nothing is redundant and the most decision-relevant fact (what comes back) is front-loaded.

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?

With an output schema present and full schema coverage, the description need not explain return formatting, and it correctly stays high-level. It is complete for a read-only singleton, though a note on the privilege level required to read the PSK would close the remaining gap.

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 output/server/raw_json/extra_params semantics are already fully documented in the schema. The description's only contribution is the negative statement that there are 'no filtering options,' which is mild added value. Baseline 3 is appropriate.

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 then enumerates exactly what is returned: the PSK identity/key and the TLS accept mode. It also distinguishes itself from sibling *_get tools by declaring it is a singleton with no filtering options.

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 rather than stated: because it is a singleton, there is no alternative autoregistration getter to choose between, and the description says so. However, it never states prerequisites (e.g. admin privileges needed to read the PSK) or explicitly when an agent should call this versus a raw API call, beyond the extra_params note in the schema.

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