Skip to main content
Glama
initMAX

Zabbix MCP Server

graphprototype_get

Read-only

Retrieve Zabbix graph prototypes used by LLD rules to generate graphs for discovered entities, with filters for hosts, templates, or discovery rules.

Instructions

Retrieve graph prototypes. Graph prototypes are used by LLD rules to create real graphs for each discovered entity, visualizing data from item prototypes.

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: discover, flags (7.4+), graphid, graphtype, height, name, percent_left, percent_right, show_3d, show_legend, show_triggers, show_work_period, templateid, uuid (6.0+), width, yaxismax, yaxismin, ymax_itemid, ymax_type, ymin_itemid, ymin_type. Text properties cannot be filtered; use 'search' for them.
outputNoProperties of the graphprototype 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: graphid, name. Properties: discover, flags (7.4+), graphid, graphtype, height, name, percent_left, percent_right, show_3d, show_legend, show_triggers, show_work_period, templateid, uuid (6.0+), width, yaxismax, yaxismin, ymax_itemid, ymax_type, ymin_itemid, ymin_type.
searchNoReturn results whose string properties contain the given pattern (case-insensitive; '*' is a wildcard when searchWildcardsEnabled is true). Example: {"name": "web"}. Keys: name, uuid (6.0+).
serverNoTarget Zabbix server. Available: default. Defaults to 'default' if omitted.
hostidsNoReturn only graph prototypes that belong to the given hosts.
graphidsNoReturn only graph prototypes with the given IDs.
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: graphid, name, graphtype, discover (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 graph prototypes that belong to the given templates.
discoveryidsNoReturn only graph prototypes belonging to the given LLD rules.
extra_paramsNoOther native graphprototype.get parameters, merged into the request as-is. Parameters: groupids, inherited, itemids, templated. Sub-object selects (value 'extend', 'count' or a list of property names): selectDiscoveryData (7.4+), selectDiscoveryRule, selectDiscoveryRulePrototype (7.4+), selectGraphItems, selectGroups (removed in 7.2), selectHostGroups (6.2+), selectHosts, selectItems, selectTemplateGroups (6.2+), selectTemplates. 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

B3.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds domain framing but discloses no behavioral traits beyond that — no pagination/limit defaults, no return volume, no mention of the raw_json security tradeoff that matters operationally. No contradiction, but little added beyond structured data.

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?

Two compact sentences with the action front-loaded and the explanatory clause clearly secondary. No wasted wording; it just stops short of routing or operational notes.

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?

An output schema exists and the input schema is exhaustive (16 params, 100% coverage), so return values and parameter behavior are well covered elsewhere. The description supplies the conceptual model of a graph prototype; only sibling-routing guidance is missing.

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 fully documents all 16 parameters including filters, output selection, sorting, and the raw_json policy warning. The description contributes no parameter-level detail, so the baseline of 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 ('graph prototypes'), and adds domain context that these are LLD artifacts used to create real graphs per discovered entity. However, it does not distinguish itself from close siblings like graph_get, discoveryruleprototype_get, or itemprototype_get, leaving the agent to infer the differentiation.

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?

Explains what graph prototypes are and their role in LLD, which implies the use case, but gives no explicit when/when-not guidance or alternatives (e.g., when to prefer graph_get or discoveryruleprototype_get). Usage is implied rather than stated.

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