Skip to main content
Glama
initMAX

Zabbix MCP Server

by initMAX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

configuration_export

Read-only

Export Zabbix hosts, templates, and groups as YAML, XML, or JSON to back up or transfer configuration between instances.

Instructions

Export Zabbix configuration as YAML, XML, or JSON. Use this to back up or transfer hosts, templates, and other objects between Zabbix instances. Params: {"format": "yaml"|"xml"|"json", "options": {"hosts": ["id"], "templates": ["id"], "host_groups": ["id"], ...}}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYesExport parameters. Required keys: 'format' ('yaml', 'xml', or 'json') and 'options' (object specifying which entities to export by type and ID, e.g. {"hosts": ["10084"], "templates": ["10001"]}).
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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.41.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered without the description. The description adds nothing behavioral of its own, and notably omits the consequential raw_json policy/permission behavior that lives only 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.

Conciseness4/5

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

Purpose and format are front-loaded in one sentence, usage in a second. The trailing inline params dump is redundant against a 100%-covered schema but is compact and does not bloat the definition.

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, return values need not be explained, and a single required 'params' object is well described. The definition is complete enough to call correctly, though the raw_json guardrails are carried entirely 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 100%, so the schema already documents params, server, and raw_json in more depth than the description. The inline param blob restates the schema rather than adding syntax or format meaning beyond it.

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?

States a specific verb+resource (export Zabbix configuration) and enumerates the output formats, so the agent knows exactly what the tool produces. It does not name or differentiate itself from the closest sibling, configuration_importcompare, leaving that inference to the agent.

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?

Explicitly gives the use case ('back up or transfer hosts, templates, and other objects between Zabbix instances'), which tells the agent when this tool is appropriate. No when-not conditions or alternatives are offered, so it stops short of a 5.

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