Skip to main content
Glama
mhajder

Zabbix MCP Server

by mhajder

graph_get

Read-onlyIdempotent

Retrieve Zabbix graphs to visualize metric data over time. Filter by host, template, or search criteria for targeted analysis.

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 results to skip (for pagination). Requires sortfield to be set.
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.
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

Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so safety profile is clear. Description adds conceptual context but no additional behavioral traits like pagination behavior, rate limits, or data freshness.

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 sentences, front-loaded with core purpose. Efficient yet informative, though could potentially be more concise by omitting the generic graph definition.

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?

Given the existence of output schema, return values are covered. However, description lacks operational context such as pagination hints or performance considerations, which are partially in schema but not emphasized.

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 93%, so parameters are well-documented there. Description adds no extra meaning beyond the schema. Baseline of 3 is appropriate.

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?

Description clearly states 'Get graphs from Zabbix' with a specific verb and resource. Context explains what graphs are and their uses, distinguishing from sibling tools focused on other Zabbix entities.

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 explicit guidance on when to use this tool vs alternatives. No mention of prerequisites, exclusions, or when not to use. Only a generic description of graphs.

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