Skip to main content
Glama
mhajder

Zabbix MCP Server

by mhajder
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

history_get

Read-onlyIdempotent

Retrieve raw metric history from Zabbix using item IDs. Filter by time range or storage type to analyze collected data points with timestamps for detailed behavior tracking.

Instructions

Get history data from Zabbix.

Retrieves the raw metric values collected by items. History contains all individual collected data points with timestamps, allowing detailed analysis of system behavior over time.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return. Default is 100.
historyNoStorage type to read: 0=float, 1=char, 2=log, 3=unsigned, 4=text. Must match the items' value_type or Zabbix returns nothing. Detected from the items when omitted.
itemidsYesItem IDs to get history for.
sortfieldNoField to sort by (default 'clock' = timestamp).clock
sortorderNoSort direction - 'ASC' (oldest first) or 'DESC' (newest first). Default is DESC.DESC
time_fromNoUnix timestamp to get history from this time onwards.
time_tillNoUnix timestamp to get history up to this time.
count_outputNoIf true, returns only the count of matched objects as an integer.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

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

  1. Changed6 schema fields changedv0.6.0
    • addedInput schema / properties / history / anyOf
      Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / history / default
      Previous value: -0New value: +null
    • changedInput schema / properties / history / description
      Previous value: -"History type: 0=float, 1=char, 2=log, 3=unsigned, 4=text."New value: +"Storage type to read: 0=float, 1=char, 2=log, 3=unsigned, 4=text. Must match the items' value_type or Zabbix returns nothing. Detected from the items when omitted."
    • removedInput schema / properties / history / type
      Removed value: -"integer"
    • addedInput schema / properties / itemids / minItems
      Added value: +1
    • removedInput schema / properties / offset
      Removed value: -{
-  "default": 0,
-  "description": "Number of results to skip (for pagination). Requires sortfield to be set.",
-  "minimum": 0,
-  "type": "integer"
-}
  2. First observedv0.5.3

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description correctly does not contradict them. The description adds conceptual context about the nature of history data (raw values, timestamps) but does not disclose additional behavioral aspects like performance implications or permission requirements beyond what annotations provide. This is adequate given the annotation coverage.

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?

The description is two sentences, front-loaded with the core purpose ('Get history data from Zabbix') followed by an explanatory sentence. It is concise and free of redundancy, though the phrase 'allowing detailed analysis of system behavior over time' is somewhat generic and could be trimmed without losing value.

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 tool's complexity (8 parameters, required itemids) and the presence of a documented output schema, the description provides a sufficient high-level understanding. It does not explicitly mention prerequisites like time filters or default limits, but those are covered in the parameter schema. The description is complete enough for an agent to know what to expect and when to invoke it.

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 each parameter having a clear description in the input schema. The tool description itself does not describe parameters, but per the rubric, a high coverage baseline of 3 is appropriate. The description's mention of 'timestamps' and 'individual data points' hints at the time and limit parameters but does not add specific syntactic or semantic detail beyond the schema.

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?

The description clearly states the verb 'Get' and the resource 'history data from Zabbix', and distinguishes it from related tools like trend_get by specifying 'raw metric values' and 'individual collected data points with timestamps'. This makes the tool's purpose unambiguous and differentiates it from siblings.

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 gives no explicit guidance on when to use this tool versus alternatives such as trend_get, event_get, or item_get. It implies the tool is for raw history data, but it does not state when to prefer it over trends or how to combine it with other tools. An agent would have to infer usage from the description alone, which is insufficient.

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