Skip to main content
Glama
initMAX

Zabbix MCP Server

templatedashboard_get

Read-only

Retrieve dashboards that belong to Zabbix templates, filtering by template or dashboard IDs to standardize monitoring views across linked hosts.

Instructions

Retrieve dashboards that belong to templates. Template dashboards are defined on templates and automatically appear on hosts linked to those templates. This is useful for standardising monitoring views across many hosts. Filter by templateids to find dashboards belonging to specific templates, or by dashboardids for direct lookup.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return.
filterNoReturn only results whose properties exactly match the given values (a single value or a list of values per key). Example: {"status": 0} or {"status": [0, 1]}. Keys: auto_start (6.0+), dashboardid (6.0+), display_period (6.0+), name (6.0+), templateid (6.0+), uuid (6.0+). Text properties cannot be filtered; use 'search' for them.
outputNoProperties of the templatedashboard object to return. Pass 'extend' for all, 'count' for the number of matches only, or a comma-separated list of property names. Default when omitted: dashboardid, name, templateid. Properties: auto_start (6.0+), dashboardid (6.0+), display_period (6.0+), name (6.0+), templateid (6.0+), uuid (6.0+).
searchNoReturn results whose string properties contain the given pattern (case-insensitive; '*' is a wildcard when searchWildcardsEnabled is true). Example: {"name": "web"}. Keys: name (6.0+), uuid (6.0+).
serverNoTarget Zabbix server. Available: default. Defaults to 'default' if omitted.
raw_jsonNoStrips the security disclaimer preamble from the response so it is pure JSON. Default: false. Requires the bearer token to have 'allow_raw_json' explicitly enabled by an operator in the admin portal - tokens without that policy receive a PolicyError instead. WARNING: setting true bypasses the prompt-injection mitigation marker that wraps untrusted Zabbix data (host names, item descriptions, problem text). LLM clients (Claude, GPT, Cursor, ...) should leave this false; only programmatic non-LLM consumers (Python scripts, n8n workflows that json.loads the result) should set true.
sortfieldNoSort by one or more of: dashboardid, name (comma-separated for several; pair with 'sortorder'). No other property is sortable.
sortorderNoSort order: 'ASC' (ascending) or 'DESC' (descending).
countOutputNoReturn the count of matching results instead of the actual data.
searchByAnyNoIf true, return results matching ANY search field (OR). Default is ALL fields (AND).
templateidsNoReturn only dashboards that belong to the given templates.
dashboardidsNoReturn only template dashboards with the given IDs.
extra_paramsNoOther native templatedashboard.get parameters, merged into the request as-is. Sub-object selects (value 'extend', 'count' or a list of property names): selectPages (6.0+). Any other key is refused here, because Zabbix would silently ignore it. For a parameter you are sure exists on your release but is not listed, use zabbix_raw_api_call.
searchWildcardsEnabledNoIf true, enable * and ? wildcards in search patterns.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.41.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations (readOnlyHint=true, openWorldHint=true) already establish that this is a safe read against external Zabbix data, so the description need not restate safety. It adds useful domain behaviour — template dashboards are defined on templates and auto-appear on linked hosts — but says nothing about pagination, default limits, or response shape.

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?

Four sentences, front-loaded with what the tool returns, then the domain rationale, then the two filter entry points. The sentence about standardising monitoring views is motivational rather than operational but is short and aids intent selection.

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 list tool with a fully documented schema and an output schema present, the description covers purpose, domain context and primary filters adequately. The remaining gap is sibling disambiguation, which is the one thing an agent picking among 80+ *_get tools would most benefit from.

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 all 14 parameters, including templateids and dashboardids with the same semantics the description mentions. The description therefore adds essentially no parameter meaning beyond the schema; baseline 3 applies.

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 ('Retrieve') and resource ('dashboards that belong to templates') and explains the template-derived nature of the objects, which separates it conceptually from dashboard_get. However, it never names the neighbouring tools (dashboard_get, hostdashboard_get) that an agent is most likely to confuse it with.

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 final sentence gives parameter-level routing advice ('Filter by templateids ... or by dashboardids for direct lookup'), which is genuine usage guidance but about which filter to pick, not when to choose this tool over dashboard_get or hostdashboard_get. No prerequisites, no exclusions, no alternative tool named.

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