Skip to main content
Glama
mhajder

Zabbix MCP Server

by mhajder
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

graph_get

Read-onlyIdempotent

Retrieve graph data from Zabbix, filtering by host, template, or graph ID. Supports pagination and optional inclusion of related items and hosts.

Instructions

Get graphs from Zabbix.

Graphs visualize item data over time, displaying metric values in line/bar/pie charts. Graphs can be included in dashboards, reports, and custom views for data analysis.

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
searchNoDictionary with search criteria like {'name': 'CPU'}.
hostidsNoList of host IDs to get graphs from.
graphidsNoList of graph IDs to get. If empty, returns all graphs.
sortfieldNoField to sort by. A deterministic sort is required for paging to be consistent.graphid
sortorderNoSort direction - 'ASC' or 'DESC'.ASC
templateidsNoList of template IDs to get graphs from.
count_outputNoIf true, returns only the count of matched objects as an integer.
select_hostsNoIf true, include the hosts that the graphs belong to (selectHosts=extend).
select_itemsNoIf true, include the items contained in each graph (selectGraphItems=extend).
filter_paramsNoAdditional filter parameters for advanced filtering.
select_templatesNoIf true, include the templates that the graphs belong to (selectTemplates=extend).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

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

  1. Changed5 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."
    • removedInput schema / properties / sortfield / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • changedInput schema / properties / sortfield / default
      Previous value: -nullNew value: +"graphid"
    • 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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safe retrieval nature is captured. The description's 'Get graphs' is consistent with those annotations but adds no further behavioral context beyond what annotations and the input schema already provide.

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

Conciseness3/5

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

The core instruction 'Get graphs from Zabbix' is front-loaded and clear. However, the two sentences about dashboards, reports, and custom views are conceptual filler that do not materially help an agent select or invoke the tool correctly.

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?

Given the rich input schema with all optional parameters and an existing output schema, the tool is sufficiently documented for correct invocation. The description could be more complete by naming sibling tools, but the structured metadata carries the remaining load.

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 about 93%, and the input schema already documents most parameter semantics, including limit, offset, search, hostids, graphids, sortfield, select_hosts, select_items, and select_templates. The description adds no additional parameter explanation, so the baseline score of 3 applies.

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?

Opens with 'Get graphs from Zabbix' - a specific verb and resource that clearly distinguishes graph_get from the many sibling *_get tools. The additional context about graphs visualizing item data over time further clarifies the resource domain.

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?

The description provides useful background ('Graphs visualize item data over time') but never explains when an agent should use graph_get versus alternative tools like item_get or history_get. There is no when-not guidance or explicit alternative routing.

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