Skip to main content
Glama
mhajder

Zabbix MCP Server

by mhajder
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

configuration_import

Imports hosts, templates, and other Zabbix configurations from JSON, XML, or YAML content. Use for migration, cloning, or restoring configurations.

Instructions

Import configurations into Zabbix.

Imports hosts, templates, and other configurations from JSON, XML or YAML. Useful for migration, cloning, or restoring configurations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rulesNoPer-object import rules, e.g. {'hosts': {'createMissing': true, 'updateExisting': true}}. Defaults to creating and updating every object type, without deleting anything.
contentYesConfiguration content to import.
format_typeNoImport format: 'json', 'xml' or 'yaml'.json
delete_missingNoIf true, the default rules also delete objects absent from the import. Ignored when 'rules' is given.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changedv0.6.0
    • addedInput schema / properties / delete_missing
      Added value: +{
+  "default": false,
+  "description": "If true, the default rules also delete objects absent from the import. Ignored when 'rules' is given.",
+  "type": "boolean"
+}
    • changedInput schema / properties / format_type / description
      Previous value: -"Import format: 'json' or 'xml'."New value: +"Import format: 'json', 'xml' or 'yaml'."
    • addedInput schema / properties / rules
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Per-object import rules, e.g. {'hosts': {'createMissing': true, 'updateExisting': true}}. Defaults to creating and updating every object type, without deleting anything."
+}
  2. First observedv0.5.3

TDQS

A3.5/5.0
Behavior2/5

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

The annotations already indicate the tool is not read-only, but the description adds no further behavioral disclosure. It does not warn that importing can overwrite existing objects or delete missing ones when configured, which is important for a bulk import tool.

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?

The description is brief, front-loaded, and free of filler. Every sentence contributes either the operation, the scope, or the intended use cases.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is sufficient for recognizing the tool, but it omits important behavioral context such as the ability to update existing objects or delete absent ones. The output schema covers return values, so the main gap is around side effects and destructive potential.

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 all parameters. The description adds mild context by naming hosts/templates and JSON/XML/YAML, but it does not explain rules or delete_missing behavior beyond what the schema provides.

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?

The description clearly identifies the operation as importing configurations into Zabbix and specifies resource types such as hosts and templates. It is easy to distinguish from export and individual CRUD tools, though it does not explicitly name or contrast any sibling tool.

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 provides concrete use cases: migration, cloning, and restoring configurations. It does not mention when not to use the tool or explicitly recommend alternatives like configuration_export or individual create/update tools.

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