Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

Template Create

template_create

Create a Zabbix template to define reusable monitoring configurations (items, triggers, graphs) for standardized monitoring across hosts.

Instructions

Create a new template in Zabbix.

Templates define the monitoring configuration (items, triggers, graphs) that can be reused across multiple hosts. Creating custom templates enables standardized monitoring for specific applications or server types.

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": {
      "host": "<host>",
      "groups": "<groups>"
    },
    "name": "template_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesTechnical name of the template.
nameNoTemplate name (required). Example: 'Apache Web Server', 'PostgreSQL Database'. Should describe what the template monitors.
groupsYesTemplate groups the template belongs to, e.g. [{'groupid': '10'}]. Since Zabbix 6.2 these are template groups, not host groups.
descriptionNoOptional template description explaining its purpose and use.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.0
    • changedInput schema / properties / groups / description
      Previous value: -"Host groups."New value: +"Template groups the template belongs to, e.g. [{'groupid': '10'}]. Since Zabbix 6.2 these are template groups, not host groups."
  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 already declare readOnlyHint=false and idempotentHint=false, so the write nature is covered, but the description adds no behavioral context beyond that. It does not mention that repeated calls create duplicates, that the 'host' technical name must be unique, or what happens when a group id is invalid.

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?

Front-loaded with the action in the first sentence, with the explanatory paragraph following. The conceptual explanation is slightly verbose for a tool definition but not wasteful.

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?

With annotations, an output schema, and full schema coverage, the structured data covers most needs, but for a non-idempotent create operation the description omits uniqueness constraints and group-existence prerequisites, leaving a meaningful gap.

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 four parameters are fully documented in the schema, and the description adds no parameter-level detail. Baseline 3 applies when the schema carries the burden.

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?

States a specific verb and resource ('Create a new template in Zabbix') and clarifies what a template is, making it easy to distinguish from template_get, template_update, and template_delete. The second paragraph adds domain meaning without obscuring the action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description explains why templates are useful but never states when to choose this tool over siblings (e.g., template_update for existing templates), nor does it mention prerequisites such as groups needing to exist first. Usage is only inferable from the verb.

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