Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

Host Create

host_create

Adds a new monitored host to Zabbix using a host name and groups, with optional interfaces and templates to start monitoring servers or devices.

Instructions

Create a new host in Zabbix.

Adds a new monitored host to Zabbix. This is essential for starting to monitor a new server or device. You must specify at least a host name and groups. You can optionally configure interfaces (for agent/SNMP communication) and link templates.

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": "host_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostNoTechnical name of the host.
nameNoVisible name.
groupsNoHost groups (e.g., [{'groupid': '1'}]).
paramsNoRaw host.create params, for fields the arguments below do not cover. Describes a single host, not a batch. If provided, individual parameters are ignored.
statusNo0=enabled, 1=disabled.
templatesNoTemplates to link.
interfacesNoHost interfaces.
descriptionNoDescription.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.0
    • changedInput schema / properties / params / description
      Previous value: -"Raw params dict for bulk operations. If provided, individual parameters are ignored."New value: +"Raw host.create params, for fields the arguments below do not cover. Describes a single host, not a batch. If provided, individual parameters are ignored."
  2. First observedv0.5.3

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare non-readOnly, non-idempotent, non-destructive, so the safety profile is covered by structured data. The description adds the practical requirement that a host name and groups are mandatory and that interfaces/templates are optional, which is useful context beyond annotations, but says nothing about duplicate-name behavior, permissions, or side effects of attaching templates.

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?

Short and front-loaded, opening with the action and then requirements. The second sentence ('Adds a new monitored host to Zabbix') largely restates the first, a minor redundancy, but the remainder each contributes a distinct constraint or capability.

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

Completeness5/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 described, and the description covers the effective required fields plus the optional interfaces and template linkage that define a create call. Combined with full schema coverage and annotations, an agent has enough to invoke it correctly.

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 coverage is 100%, so the schema already documents all eight parameters, making 3 the baseline. The description's note that host name and groups are effectively required (despite zero formally required fields) is a genuinely useful addition, but interfaces, templates, status, and the raw 'params' passthrough are not explained further.

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 ('Create a new host in Zabbix') and clarifies it adds a monitored host, so an agent knows what object is produced. It never names or contrasts with siblings like host_update or host_get, so differentiation relies on the agent inferring from names.

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?

The phrase 'essential for starting to monitor a new server or device' implies the situation in which to use it, but there is no explicit when-not-to-use or reference to the update/get/delete siblings. Adequate but leaves the agent to infer the boundary between create and update.

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