Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

History Get

history_get
Read-onlyIdempotent

Retrieve raw metric values collected by Zabbix items with timestamps to analyze system behavior over time; filter by item IDs, time range, sort order, and result limit.

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "itemids": "<itemids>"
    },
    "name": "history_get"
  }
}

Input 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

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  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?

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds that results are raw individual collected data points with timestamps, but does not discuss volume, performance, or pagination behavior beyond what the schema already documents.

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 short and front-loaded with the core action. The second sentence is helpful but slightly overlaps with the first by restating that history contains individual data points.

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 an output schema, full schema description coverage, and annotations covering safety, the description is complete enough for an agent to understand that this tool returns raw historical metric values. Minor missing context includes explicit guidance versus trend_get, but the structured fields carry the detailed contract.

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%, so all eight parameters are documented in the schema, including history type matching, time filters, sorting, limit, and count_output. The description adds no parameter-specific meaning beyond the schema, so baseline 3 is appropriate.

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 and resource: retrieves raw metric values collected by items from Zabbix, with timestamps. It implicitly distinguishes history from aggregate trend data by emphasizing individual raw data points, but does not explicitly name alternatives like trend_get.

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?

Provides implied usage for detailed system behavior analysis over time, but does not state when to use this instead of sibling tools such as trend_get or item_get, nor does it give exclusions or prerequisites.

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