Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

Configuration Import

configuration_import
Destructive

Imports hosts, templates, and other Zabbix configurations from JSON, XML, or YAML to migrate, clone, or restore setups.

Instructions

Import configurations into Zabbix.

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

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "content": "<content>"
    },
    "name": "configuration_import"
  }
}

Input 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

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  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

B3.2/5.0
Behavior2/5

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

Annotations flag destructiveHint=true and idempotentHint=false, yet the description never mentions that an import can overwrite or delete existing objects, nor that repeated imports are not idempotent. For a destructive bulk-mutation tool this silence is a significant gap – the description adds no behavioural context beyond the annotations themselves.

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?

Two short sentences, front-loaded with the operation and resource, with no filler. The second line about formats is slightly redundant with the schema but does not waste much space.

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?

An output schema exists so return values need not be explained, and the schema covers parameters well. However, given a destructive, non-idempotent bulk import across many object types, the description omits any warning about overwrite/delete behaviour or conflict handling that an agent would need before invoking it.

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 'content', 'format_type', 'rules' and 'delete_missing' thoroughly, including the interaction between them. The description's mention of JSON/XML/YAML merely restates what the schema says, so the baseline holds.

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 and resource ('Import configurations into Zabbix') and enumerates the object types and accepted formats, which is more than the title alone provides. It does not differentiate itself from the obvious sibling configuration_export, but the import/export split is self-evident.

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?

Gives usage contexts ('migration, cloning, or restoring') but no when-not guidance, no pointer to configuration_export or to per-object tools, and no prerequisites. Usage is implied rather than directed.

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