Skip to main content
Glama
mhajder

Zabbix MCP Server

by mhajder
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

template_get

Read-onlyIdempotent

Fetches templates from Zabbix, standardizing items, triggers, and graphs for reuse. Solves inconsistent monitoring by applying consistent configurations across multiple 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 matching records to skip. Use with 'limit' to page through results; check 'has_more' and 'total' in the response.
outputNoextend
searchNoSubstring search in template name. Matches partial names like 'Linux' finds 'Linux Server Template'.
hostidsNo
groupidsNo
sortfieldNoField to sort by. A deterministic sort is required for paging to be consistent.host
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 (selectTemplateGroups=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

Schema Changelog

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

  1. Changed6 schema fields changedv0.6.0
    • changedInput schema / properties / offset / description
      Previous value: -"Number of results to skip (for pagination). Requires sortfield to be set."New value: +"Number of matching records to skip. Use with 'limit' to page through results; check 'has_more' and 'total' in the response."
    • changedInput schema / properties / select_groups / description
      Previous value: -"If true, include the template groups the templates belong to (selectGroups=extend)."New value: +"If true, include the template groups the templates belong to (selectTemplateGroups=extend)."
    • removedInput schema / properties / sortfield / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • changedInput schema / properties / sortfield / default
      Previous value: -nullNew value: +"host"
    • changedInput schema / properties / sortfield / description
      Previous value: -"Field to sort by."New value: +"Field to sort by. A deterministic sort is required for paging to be consistent."
    • addedInput schema / properties / sortfield / type
      Added value: +"string"
  2. First observedv0.5.3

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare this as read-only, idempotent, and non-destructive, so the description does not need to restate those. It adds useful context about templates being reusable collections and standardizing monitoring, which helps the agent understand the domain. It could mention response structure details, but the output schema exists, so not mandatory. No contradiction with annotations.

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 concise: a single sentence stating the core action, followed by a short explanation of templates. It is front-loaded with the main purpose, and the additional context is useful. No filler or redundancy.

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?

For a read-only getter with a rich schema (16 parameters, many with descriptions) and an output schema, the description covers the essential what and why. It does not detail every parameter, but the schema fills that gap. Considering the complexity, the description is adequate and complete enough for an agent to use the tool correctly without needing additional context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 81%, so the schema already documents most parameters. The description adds value by explaining the concept of templates and the 'search' parameter behavior with an example, which goes beyond the schema. It also clarifies practical usage hints like paging with 'limit' and 'offset'. This justifies a score above baseline 3.

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 states a specific verb ('Get') and resource ('templates from Zabbix') and further clarifies what templates are, distinguishing this getter from sibling tools like template_create, template_delete, and template_update. This makes the tool's purpose unambiguous.

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 and their role in standardizing monitoring, giving context for when this tool is relevant. However, it does not explicitly state when to choose this over other getters (e.g., host_get) or when not to use it. Usage is implied but not explicit.

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