Skip to main content
Glama
Sign In
Zabbix MCP Server

Zabbix MCP Server

by initMAX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

graphitem_get

Read-only

Retrieve graph items to inspect the individual data series in a Zabbix graph, including item links, colors, draw styles, sort order, and Y-axis side. Filter by graph or item.

Instructions

Retrieve graph items (read-only). Graph items are the individual data series within a graph. Each graph item links a Zabbix item to a graph, specifying color, draw style, sort order, and Y-axis side.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return.
outputNoProperties of the graphitem object to return. Pass 'extend' for all, 'count' for the number of matches only, or a list of property names. Default when omitted: gitemid, graphid, itemid, color. Properties: calc_fnc, color, drawtype, gitemid, graphid, itemid, sortorder, type, yaxisside.
serverNoTarget Zabbix server. Available: default. Defaults to 'default' if omitted.
itemidsNoReturn only graph items that reference the given items.
graphidsNoReturn only graph items that belong to the given graphs.
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: gitemid (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.
extra_paramsNoOther native graphitem.get parameters, merged into the request as-is. Parameters: type. Sub-object selects (value 'extend', 'count' or a list of property names): selectGraphs. 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 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",
+        "preservekeys",
+        "type",
+        "selectGraphs"
+      ]
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / output / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "extend",
+      "count"
+    ],
+    "type": "string"
+  },
+  {
+    "items": {
+      "enum": [
+        "calc_fnc",
+        "color",
+        "drawtype",
+        "gitemid",
+        "graphid",
+        "itemid",
+        "sortorder",
+        "type",
+        "yaxisside"
+      ],
+      "type": "string"
+    },
+    "minItems": 1,
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / output / description
      Previous value: -"Properties of the graphitem 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: gitemid, graphid, itemid, color. Properties: calc_fnc, color, drawtype, gitemid, graphid, itemid, sortorder, type, yaxisside."New value: +"Properties of the graphitem object to return. Pass 'extend' for all, 'count' for the number of matches only, or a list of property names. Default when omitted: gitemid, graphid, itemid, color. Properties: calc_fnc, color, drawtype, gitemid, graphid, itemid, sortorder, type, yaxisside."
    • changedInput schema / properties / sortfield / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "gitemid"
+    ],
+    "type": "string"
+  },
+  {
+    "items": {
+      "enum": [
+        "gitemid"
+      ],
+      "type": "string"
+    },
+    "minItems": 1,
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / sortfield / description
      Previous value: -"Sort by one or more of: gitemid (comma-separated for several; pair with 'sortorder'). No other property is sortable."New value: +"Sort by one or more of: gitemid (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": "graphitem_getOutput",
-  "type": "object"
-}New value: +null
  2. 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 already declare readOnlyHint=true and openWorldHint=false, so the "(read-only)" note adds nothing and the safety bar is already met elsewhere. The description contributes genuine domain context (what a graph item is composed of) but says nothing about result volume, pagination, default field selection, or permission requirements — details that happen to live in the schema rather than the description.

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?

Three short sentences, front-loaded with the action and followed by the entity definition; no wasted wording. The only redundancy is the parenthetical "(read-only)", which repeats the annotation.

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, all-optional-parameter list tool with full schema documentation and no output schema, the description covers purpose and entity semantics adequately, and the schema covers defaults and filtering. It is only slightly thin on how the returned records relate to sibling tools (graph_get, item_get) that an agent may need to chain with.

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%, with limit, output, server, itemids, graphids, sortfield/sortorder, countOutput, raw_json, and extra_params all documented in-schema, so the baseline is 3. The description adds no filter or output-mode guidance of its own, leaving the schema to do all the work.

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?

The description gives a specific verb and resource ("Retrieve graph items") and defines the entity precisely: "the individual data series within a graph" linking a Zabbix item to a graph with color, draw style, sort order, and Y-axis side. This clearly separates it from the graph-level sibling (graph_get), though that sibling is never named explicitly.

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?

Usage is only implied: an agent can infer it fetches graph-item membership records, useful when it already knows a graphid or itemid. There is no explicit statement of when to prefer this over graph_get or graphprototype_get, and no note that it is the lookup path from item to graph (or graph to item), which is the main decision an agent faces here.

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

Deploy Server

Other Tools