Skip to main content
Glama
mhajder

Zabbix MCP Server

by mhajder

template_get

Read-onlyIdempotent

Get Zabbix templates for standardized monitoring. Search by name, ID, or group, and include linked hosts or macros to apply consistent monitoring across servers.

Instructions

Get templates from Zabbix.

Templates are reusable collections of items, triggers, and graphs that can be applied to hosts. They standardize monitoring across multiple servers with the same role.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return. Default is 100.
offsetNoNumber of results to skip (for pagination). Requires sortfield to be set.
outputNoextend
searchNoSubstring search in template name. Matches partial names like 'Linux' finds 'Linux Server Template'.
hostidsNo
groupidsNo
sortfieldNoField to sort by.
sortorderNoSort direction - 'ASC' or 'DESC'.ASC
select_tagsNoIf true, include the tags for the templates (selectTags=extend).
templateidsNoList of template IDs to get. If empty, returns all templates. Find template IDs with a search or from host associations.
count_outputNoIf true, returns only the count of matched objects as an integer.
select_hostsNoIf true, include the hosts that are linked to the templates (selectHosts=extend).
select_groupsNoIf true, include the template groups the templates belong to (selectGroups=extend).
select_macrosNoIf true, include the macros for the templates (selectMacros=extend).
select_templatesNoIf true, include the templates that are linked to these templates directly (selectTemplates=extend).
template_name_containsNoShortcut to search for templates by name (constructs search={'host': template_name_contains}).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds no behavioral context beyond the annotations, repeating only what a template is. Minor additional value.

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?

The description is three sentences long, with the first sentence front-loading the core purpose. The subsequent explanatory sentence provides context without being verbose. Slightly improved by trimming the explanatory part.

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?

The tool has a rich input schema and an output schema (implied by context), so the description does not need to explain return values. It adds context about templates' purpose, which is helpful. No major gaps given the structured fields.

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 81%, so baseline 3. The main description does not add extra meaning beyond the parameter descriptions in the schema. Parameters are adequately documented in the schema itself.

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 clearly states 'Get templates from Zabbix' with a specific verb and resource. It distinguishes from sibling tools like template_create, template_delete, and template_update, which imply mutation.

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 description explains what templates are but provides no explicit guidance on when to use this tool versus alternatives (e.g., host_get, item_get). Usage is implied but not clarified.

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