Skip to main content
Glama
mhajder

Zabbix MCP Server

by mhajder

configuration_export

Read-onlyIdempotent

Export Zabbix hosts and templates with all associated items, triggers, and configuration elements to JSON, XML, or YAML for backup and migration.

Instructions

Export Zabbix configurations.

Exports monitored hosts, templates, and their complete configurations to JSON, XML, or YAML format. Useful for backup, migration, disaster recovery, or sharing configurations.

When you export templates or hosts, the export includes:

  • All associated items (metrics/data sources)

  • All triggers and their dependencies

  • Discovery rules and prototypes

  • Graphs and visualizations

  • Macros and variable definitions

  • Host groups and interfaces (for hosts)

  • Inventory data (for hosts)

  • And all other configuration elements

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostidsNoList of host IDs to export.
format_typeNoExport format: 'json', 'xml', or 'yaml'.json
prettyprintNoIf true, returns pretty-printed output.
templateidsNoList of template IDs to export.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds valuable context about the contents of the export (items, triggers, etc.) without contradicting annotations.

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?

The description is well-structured with a brief introductory sentence followed by a bulleted list of included elements. It is moderately concise and front-loads the core purpose.

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?

Given the presence of output schema (which details return format) and comprehensive annotations, the description is sufficiently complete. It explains the scope of export (what is included) which is essential for a complex export tool.

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%. The description reiterates that hostids and templateids are for selecting hosts/templates but does not add significant new meaning beyond the schema.

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 clearly states it exports Zabbix configurations (verb 'export', resource 'configurations'), lists what is included, and distinguishes from sibling tools like configuration_import.

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?

The description explicitly mentions use cases: backup, migration, disaster recovery, or sharing configurations. It does not mention when not to use or alternatives, but the context is clear and sibling tools provide contrast.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mhajder/zabbix-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server