Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

Configuration Export

configuration_export
Read-onlyIdempotent

Export Zabbix hosts, templates, and complete configurations to JSON, XML, or YAML for backup, migration, disaster recovery, or sharing.

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

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "configuration_export"
  }
}

Input 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

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.3

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description earns credit by disclosing the scope of what gets pulled in (items, triggers, discovery rules, graphs, macros, host groups, inventory), which tells the agent the output is large and cascading. It does not state what happens when both hostids and templateids are omitted, which is the main behavioral unknown.

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?

Purpose is front-loaded in the first line, followed by the format/output summary and then a scannable inclusion list. The only filler is the closing 'And all other configuration elements', which is forgivable as a catch-all.

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 a full input schema, an output schema, and read-only annotations, the description covers what an agent needs to invoke it correctly. The one gap is default behavior with zero IDs (export everything vs. error), which matters because no parameters are required.

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 is 3; the description adds real meaning on top by explaining that exporting a host or template transitively includes its dependent objects, which reframes what hostids/templateids actually select. It does not explain the interaction of the two ID lists or the validation of format_type values beyond what the schema lists.

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 opens with a specific verb+resource ("Export Zabbix configurations") and immediately narrows to hosts, templates, and their full configuration, which distinguishes it cleanly from the sibling configuration_import and from the many *_get tools that return single-object data. An agent can pick this 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 Guidelines4/5

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

It gives clear use contexts: backup, migration, disaster recovery, and sharing configurations. It does not name exclusions or point at a specific alternative (e.g. 'use configuration_import to restore', or 'use host_get for a single host'), so it stops short of full routing guidance.

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