Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

graphprototype_get

Read-only

Retrieves graph prototypes used by LLD rules to define real graphs for discovered entities, enabling visualization of item prototype data.

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

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 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 (a list 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: groupCount, groupids, inherited, itemids, templated. Switches (true turns one on, false is the same as leaving it out): groupCount. groupCount goes with output='count': the count is then split by the ID filters the method groups by (hostids, groupids ...), one row per ID with 'rowscount'; a single row without such a filter. 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv1.42.2
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / extra_params / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "propertyNames": {
      +      "enum": [
      +        "editable",
      +        "excludeSearch",
      +        "preservekeys",
      +        "startSearch",
      +        "groupCount",
      +        "groupids",
      +        "inherited",
      +        "itemids",
      +        "templated",
      +        "selectDiscoveryData",
      +        "selectDiscoveryRule",
      +        "selectDiscoveryRulePrototype",
      +        "selectGraphItems",
      +        "selectGroups",
      +        "selectHostGroups",
      +        "selectHosts",
      +        "selectItems",
      +        "selectTemplateGroups",
      +        "selectTemplates"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / extra_params / description
      Previous value: -"Other 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."New value: +"Other native graphprototype.get parameters, merged into the request as-is. Parameters: groupCount, groupids, inherited, itemids, templated. Switches (true turns one on, false is the same as leaving it out): groupCount. groupCount goes with output='count': the count is then split by the ID filters the method groups by (hostids, groupids ...), one row per ID with 'rowscount'; a single row without such a filter. 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."
    • changedInput schema / properties / filter / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "propertyNames": {
      +      "enum": [
      +        "discover",
      +        "flags",
      +        "graphid",
      +        "graphtype",
      +        "height",
      +        "name",
      +        "percent_left",
      +        "percent_right",
      +        "show_3d",
      +        "show_legend",
      +        "show_triggers",
      +        "show_work_period",
      +        "templateid",
      +        "uuid",
      +        "width",
      +        "yaxismax",
      +        "yaxismin",
      +        "ymax_itemid",
      +        "ymax_type",
      +        "ymin_itemid",
      +        "ymin_type"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / output / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "extend",
      +      "count"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "discover",
      +        "flags",
      +        "graphid",
      +        "graphtype",
      +        "height",
      +        "name",
      +        "percent_left",
      +        "percent_right",
      +        "show_3d",
      +        "show_legend",
      +        "show_triggers",
      +        "show_work_period",
      +        "templateid",
      +        "uuid",
      +        "width",
      +        "yaxismax",
      +        "yaxismin",
      +        "ymax_itemid",
      +        "ymax_type",
      +        "ymin_itemid",
      +        "ymin_type"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / output / description
      Previous value: -"Properties 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."New value: +"Properties of the graphprototype object to return. Pass 'extend' for all, 'count' for the number of matches only, or a 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."
    • changedInput schema / properties / search / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "propertyNames": {
      +      "enum": [
      +        "name",
      +        "uuid"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / sortfield / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "graphid",
      +      "name",
      +      "graphtype",
      +      "discover"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "graphid",
      +        "name",
      +        "graphtype",
      +        "discover"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / sortfield / description
      Previous value: -"Sort by one or more of: graphid, name, graphtype, discover (comma-separated for several; pair with 'sortorder'). No other property is sortable."New value: +"Sort by one or more of: graphid, name, graphtype, discover (a list for several; pair with 'sortorder'). No other property is sortable."
    • changedInput schema / properties / sortorder / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "ASC",
      +      "DESC"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "ASC",
      +        "DESC"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "result": {
      -      "title": "Result",
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "result"
      -  ],
      -  "title": "graphprototype_getOutput",
      -  "type": "object"
      -}New value: +null
  2. First observedv1.41.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds domain context about LLD-created graphs but no behavioral details such as pagination, default output, or permission requirements; for a read-only getter this is a minor gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the action and followed by a compact domain explanation. No filler or redundancy.

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?

The tool has 16 optional parameters and no output schema, and the description covers the entity's purpose but not invocation-level concerns like default output fields, count mode, or raw_json policy. Since the schema is fully documented, this is adequate but not rich; the main missing piece is routing versus graph_get.

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% and all 16 parameters have detailed descriptions, including filter, output, search, raw_json, and extra_params. The description adds no parameter semantics beyond the schema, so 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 (graph prototypes), and the second sentence explains their LLD role, which distinguishes them conceptually from real graphs. It does not explicitly name graph_get or other sibling get tools, so sibling differentiation is only partial.

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?

No when-to-use, when-not-to-use, or alternative tool is named. The LLD context implies these are template/discovery prototypes rather than real graphs, but the agent must infer that graph_get is the tool for actual graphs.

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